Ensure subject DN is stored into db with the expected format (RFC2253) #791
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
enricovianello
changed the title
|
Move to iam-common duplicated code
enricovianello
force-pushed
the
fix-incorrect-dn-format
branch
from
c2c452b to
860ce57
Compare
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.
https://datatracker.ietf.org/doc/html/rfc2253
The target of this PR is ensuring that each time a x509 certificate is added (via SCIM PATCH) or linked (during login phase) its subject and issuer are stored in the same way, following RFC 2253. Also the search logic has to be able to "normalize" a received subject to the same RFC, in order to avoid case-insensitive problems.