GAM-team / GAM-team/got-your-back
Service account not auth'ing as expected
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 245
- PR merge metrics
- No merged PRs in 30d
Description
The issue tracker is for reporting product deficiencies. How do I questions should be posted to the discussion forum at https://groups.google.com/group/got-your-back. When in doubt, start at the discussion forum and return here only when instructed to do so.
Please confirm the following:
- I have upgraded to the latest GYB release from https://github.com/jay0lee/got-your-back/releases and I still have this issue.
Yes, this is a fresh install - I am typing the command as described in the GAM Wiki at https://github.com/jay0lee/got-your-back/wiki
Yes, although the Wiki has steps that seem to be automatically done during setup, such as creating the oauth2service json file
Full steps to reproduce the issue:
- Added the necessary scopes and waited. It's still an issue after about 30 minutes
- Hit 'y' during setup for admin use and entered a user's email address
- Received the error below. The same occurs when running
check-service-accountoutside of setup
Expected outcome (what are you trying to do?): Use a service account
Actual outcome (what errors or bad behavior do you see instead?):
Checking service account DwD for user@domain.com...
Please run
gyb --action create-project
gyb --action check-service-account
to create and configure a service account.
ERROR: None
gyb --action create-project --email user@domain.com
File C:\GYB\oauth2service.json already exists. Please delete or rename it before attempting to create another project.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the check-service-account and create-project actions described in the report, reproducing the failure after a fresh install. Inspect how these actions use C:\GYB\oauth2service.json, including the existing-file condition, and verify that a configured service account can authenticate for the specified user without the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100