-
Notifications
You must be signed in to change notification settings - Fork 133
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
Force galaxy session auth as the first auth class. #2279
Force galaxy session auth as the first auth class. #2279
Conversation
No-Issue Signed-off-by: James Tanner <[email protected]>
No-Issue Signed-off-by: James Tanner <[email protected]>
No-Issue Signed-off-by: James Tanner <[email protected]>
No-Issue Signed-off-by: James Tanner <[email protected]>
Backport to stable-4.10: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply 64968a9 on top of patchback/backports/stable-4.10/64968a924ab03a85c7072dbee60e9d450acd2d09/pr-2279 Backporting merged PR #2279 into master
🤖 @patchback |
Backport to stable-4.10: 💚 backport PR created✅ Backport PR branch: Backported as #2319 🤖 @patchback |
The galaxy sessionauth class must always come first to control the 401 vs 403 error messages AND to prevent the keycloak auth classes from sending back a www-authenticate header that causes an authentication popup in the platform UX. No-Issue Signed-off-by: James Tanner <[email protected]> (cherry picked from commit 64968a9)
…s the first auth class. (#2319) Force galaxy session auth as the first auth class. (#2279) The galaxy sessionauth class must always come first to control the 401 vs 403 error messages AND to prevent the keycloak auth classes from sending back a www-authenticate header that causes an authentication popup in the platform UX. No-Issue Signed-off-by: James Tanner <[email protected]> (cherry picked from commit 64968a9) Co-authored-by: jctanner <[email protected]>
https://issues.redhat.com/browse/AAP-32146