root: add setting to configure primary django hasher #10195
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
✅ Deploy Preview for authentik-storybook canceled.
|
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
I'm curious as to the use case of this. Do you have custom scripts or things that sync that password back to LDAP? |
That will be the case since the performance of integrated ldap provider isn't fast / stable enough for our use case (user login to central server systems via sssd). Besides we only need to provide some users via LDAP. I thought about adding a filter to the integrated LDAP provider, but I think OpenLDAP is more stable / faster. |
|
@rissson I there a chance of getting this merged? |
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.
Details
This pull request makes the primary django hasher configurable via the .env file. I would like to switch the internal hash algorithm to Argon2, due to its compatibility with OpenLDAP. There is no breaking change and the parameter is optional. If not set, the standard django hasher hierarchy is used. I couldn't test it with the current main since the
ak servercommands gets stuck during migration processes (see #9866). It is tested with 2024.04.Checklist
ak test authentik/) -> no because main is currently broken, tests are failing before changing anything, at least for memake lint-fix)If an API change has been made
The API schema has been updated (-> no API changesmake gen-build)If changes to the frontend have been made
The code has been formatted (-> no frontend changesmake web)If applicable
make website)