When the credential provider runs the login stub application, it needs to create a new user 'gaia' with limited access to perform the actual signin procress. It is possible that this user name will already be used on machines where the GCPW is deployed so it might be worth looking into making the username generation for this account more robust.

Possible solutions include:
- Create a new user each time the GCPW is executed
- Check for a valid unused user name and store that into the secure storage area along with the PW for the username
- Use a more obfuscated name where the possibility that another username will clash is less likely.

We will also probably want to perform some checks on the final user that is generated to ensure it has the correct permissions (e.g. not admin)