Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove reference to nonexistent workload identity functionality #166

Merged
merged 2 commits into from
Apr 11, 2024

Conversation

irons
Copy link
Contributor

@irons irons commented Mar 28, 2024

The Google connector docs' reference to relying on GKE Workload Identity, instead of hardcoding service account credentials, was merged as part of PR 138. One of the PRs it documents, 2989, implements that functionality, but has been open for ten months.

I would prefer to see PR 2989 merged without delay, and that functionality promptly released, after which this PR could be closed without merging. Failing that, this PR should be merged to remove the inaccurate claim of support for Workload Identity from the Google connector docs. There are several people in the 2989 discussion who've been misled by it, as was I.

Thanks for your time.

Copy link
Member

@nabokihms nabokihms left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's merge this PR for now. Thank you.

@nabokihms nabokihms merged commit 7502321 into dexidp:main Apr 11, 2024
5 checks passed
@StepanKuksenko
Copy link

@irons @nabokihms seems like this PR can be reverted because the Google Workload Identity functionality was merged in dexidp/dex#2989

@renan
Copy link

renan commented Nov 22, 2024

@StepanKuksenko This can be reverted, indeed. I've just tested it out and it works when not providing the JSON

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants