Update mokey_oidc readme to include OIDC configuration without Mokey/Hydra integration #528
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
…Hydra integration
aebruno
approved these changes
Jul 21, 2023
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.
I had an issue with using
mozilla-django-oidcwas that the user would log in with OIDC, get redirected to our provider, but ultimately get returned to the login failure url (/by default) and not get logged in. The problem was that thesessionidcookie was not getting returned to us in Firefox, because theSESSION_COOKIE_SAMESITEsetting is set to"Strict"in ColdFront's default settings inauth.py.I fixed the problem by changing the setting to
"Lax".Also removed an extra newline at the start of the code block.