Enable openidconnect-rs feature to support non-compliant timestamps. #12
Conversation
This file contains hidden or 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
ctron
approved these changes
Sep 22, 2025
Owner
|
Could you reformat the commit message into a conventional commit. That makes it show up in the changelog. I guess something like: |
apognu
force-pushed
the
feat/rfc3339-timestamps
branch
from
bec7e34 to
16f19bd
Compare
Contributor
Author
|
Sure thing, done. |
ctron
approved these changes
Sep 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR (related to #11) turns on a feature on the upstream
openidconnect-rsto support non-compliant timestamps in an IDP responses.Among others, it allows to use Auth0 as an IDP (which sends an invalid
updated_atfield.