-
Notifications
You must be signed in to change notification settings - Fork 189
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.
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
passwords for users created via graph is stored unhashed in idm #3778
Comments
@micbar, IMO this should have a higher priority. |
I think this would be the clean solution. Where would we add the hashing? To the ldapserver or to the handlers (boltdb, etc...)? |
If it just where about It's more difficult however as we also want to support external LDAP servers. OpenLDAP e.g. does not hash the password when add or modified via the standard LDAP operations (mainly to stay compatible with the LDAP RFC). For OpenLDAP it would makes sense set the password via the The most compatible approach might be to add |
I see, that is news to me.
Yes, this makes sense. I can take a look into that next week. |
Oh. I already started some ground work on that. (Sorry, I saw this a bit too late. Didn't want to step on your toes). See https://github.com/rhafer/idm/tree/pwexop If you want we can pair on this on monday. |
By default the graph API will now use the LDAP Password Modify Extended Operation for setting user passwords. By this we make sure that the LDAP server can e.g. properly hash the password with and algorithm that it supports. This can be reverted to the old behaviour (using "normal" LDAP modify requests) by setting GRAPH_LDAP_SERVER_USE_PASSWORD_MODIFY_EXOP=false Fixes: owncloud#3778
By default the graph API will now use the LDAP Password Modify Extended Operation for setting user passwords. By this we make sure that the LDAP server can e.g. properly hash the password with and algorithm that it supports. This can be reverted to the old behaviour (using "normal" LDAP modify requests) by setting GRAPH_LDAP_SERVER_USE_PASSWORD_MODIFY_EXOP=false Fixes: owncloud#3778
By default the graph API will now use the LDAP Password Modify Extended Operation for setting user passwords. By this we make sure that the LDAP server can e.g. properly hash the password with and algorithm that it supports. This can be reverted to the old behaviour (using "normal" LDAP modify requests) by setting GRAPH_LDAP_SERVER_USE_PASSWORD_MODIFY_EXOP=false Fixes: #3778
Describe the bug
Currently the user passwords for users created via graph are stored in cleartext in libregraph/idm (for other LDAP implementation this depends a bit on the specific configuration). We could either:
Note: the userpassword for the user
admin
and all service users are already hashed.The text was updated successfully, but these errors were encountered: