Authentik compatibility#18
Open
Rotti2 wants to merge 1 commit intoSohalt:masterfrom
Open
Conversation
…_CHECK to be compatible to Authentik
|
would be great if a fix for this issue would be merged. Using Authentik and want to use Pretix myself. |
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
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.
Authentik can work as an LDAP Identity Provider, but it does not support the LDAP attributes createTimestamp and modifyTimestamp source. By default, the ldap3 library expects these two attributes in the LDAP responses and throws an error when they are not present.
Because of that, pretix-ldap is currently not compatible with Authentik.
This pull request adds both attributes to the excluded parameters of ldap3. This should not be a problem, as pretix-ldap does not use these attributes at all.