-
Notifications
You must be signed in to change notification settings - Fork 10
LDAP Error #48
Comments
Does some of these LDAP settings help? Do you have , at LDAP group name? If yes, you could try to urlencode it: You could also search these open and closed issues does somebody else have same errors. |
I have already use the link number 1 and i have a active directory structure i have already fill all fields |
You could also google search what that error means. Does this happen with all users, or only some users? Are there some special characters in usernames? |
not special characters in username and yes for all users |
Can users login with email address and password? I think login with username does not work when LDAP is enabled. |
i have try and don't work with email |
I don't yet have Active Directory setup where I could test, it could take some days/weeks/months before I figure out how to setup it, because I have not used AD or LDAP on network of computers yet. I hope some other Wekan users that have Active Directory working can help, like @shioku wekan/wekan#2822 (comment) . Some google search results with that error point to info like this, I don't know do they help: At some point of time, I would like to add more community members GitHub usernames to https://github.com/wekan/wekan/wiki/Team so that they could help with various areas of Wekan configuration. |
Hi,
i have a error with LDAP authentification when i check with the command sudo snap logs -f wekan
i can see [INFO] Ldap connected but i obtains this after:
2019-12-30T14:14:00Z wekan.wekan[7299]: [ERROR] InvalidCredentialsError: 80090308: LdapErr: DSID-0C090421, comment: AcceptSecurityContext error, data 52e, v23f0
I hope you can help me plz
Thanks,
The text was updated successfully, but these errors were encountered: