Add Keycloak service account auth capability to ansible-galaxy #83145
+51
−29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ansibot
added
feature
sivel
force-pushed
the
galaxy-service-account-auth
branch
from
9fdb4ce
to
f69dcf1
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
mkrizek
removed
the
needs_triage
ansibot
added
the
stale_ci
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Add Keycloak service account auth capability to ansible-galaxy
Effectively, this adds a new configuration
client_secret, ultimately what seems to be a pretty minimal change.ISSUE TYPE
ADDITIONAL INFORMATION
Basic auth will be removed from console.redhat.com, service accounts will need to utilize this change for auth.
As of now, galaxy_ng doesn't support handling this auth mechanism, so while auth is successful, the granted token doesn't authorize access to anything. The result is API calls fail with a 403 currently. Galaxy will have to accept the added token header info added by CRC before this can work.
I believe this should also resolve #70019