Closed eugeneromero closed 7 years ago
Also getting this error. Happens when a more than one user logs in using LDAP.
Might be due to this recent change https://github.com/Banno/getsentry-ldap-auth/pull/13
I don't know. I thought so at first, but I'm also getting this error with version 2.0, which is from before the patch, so these two might not be related... Totally guessing tho.
For full disclosure I must add my test with 2.0 was only by changing the version number in my Chef recipe that deploys this and running in a virtual machine. Not too thorough testing, so there's a chance I might have done something wrong and I wasn't actually testing 2.0. Again, just FWIW.
Do your ldap users have mail
attributes that are unique?
Downgrading the library to 2.0 seemed to have fixed the issue. The emails seem unique. I have the following mapping:
AUTH_LDAP_USER_ATTR_MAP = {
'name': 'name',
'email': 'mail'
}
Looking down the user list email addresses seem to get populated.
thanks @barronhagerman !
Hey guys,
Not entirely sure if this is a Sentry issue, a Django issue, or an issue with the plugin. On a clean Sentry install (v 8.8.0) with only this plugin installed (tested versions 2.0 and 2.2) and Django version 1.6.11, I am able to create a new local user no problem. However, when trying to log in using an LDAP account, I get the "Oops! Something went wrong" error on the web interface, and the log throws the following error and traceback:
The new user is not registered in the auth_user or sentry_useremail tables. Not really sure where to go with this. Thank you in advance for any help you can provide!