Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Docs(authentication): Mention the case sensitivity of authenticator_map definitions #649

Merged
merged 1 commit into from
Nov 15, 2024
+4 −0
Merged

Docs(authentication): Mention the case sensitivity of authenticator_map definitions #649

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/apps/authentication/authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,6 +176,10 @@ Doing this will cause your custom module to run in place of the default module i

In this function the user claims will be a dictionary defined by the authentication_maps. You need to update the users permissions in your application based on this.

When defining authenticator maps, you will need to be mindful of the case-sensitivity of the authenticator backend's output in order to get the expected output. For example,
LDAPs authenticator plugin accepts input in a case-insensitive manner, but returns a user's group membership in a case sensitive manner
(ie. cn=John Smith,dc=example,dc=org vs CN=John Smith,DC=example,DC=org); In most cases "cn=John Smith,dc=example,dc=org" would be considered a valid group name during user claims
reconciliation, but this may depend on the specific LDAP implementation being used.

## Optional RBAC dependency

Expand Down
Loading