Bug: Creating user data failed after LDAP authentication succeed
See original GitHub issueEnvironment
Host
item | version |
---|---|
OS | ArchLinux |
crowi-plus | 2.4.5-RC |
node.js | 6.12.0 |
npm | 3.10.10 |
yarn | 1.5.1 |
Using Docker | yes (both) |
Using crowi-plus-docker-compose | yes |
LDAP Configuration
item | value |
---|---|
Server URL | ldap://ad.domain.local/cn=Users,dc=domain,dc=local |
Binding Mode | User Bind |
Bind DN | cn={{username}},cn=Users,dc=domain,dc=local |
Search Filter | (|(name={{username}})(mail={{username}})) |
LDAP(AD)
item | version |
---|---|
OS | ubuntu server 16.04 |
samba4 | Version 4.9.0pre1-GIT-e9d42e5 |
Client
item | version |
---|---|
OS | Linux |
browser | Firefox/Chrome |
How to reproduce? (再現手順)
- Launch LDAP, crowi-plus
- Access and login
What happens? (症状)
- Internal Server Error
ValidationError: User validation failed: username: Path `username` is required.
at MongooseError.ValidationError (/opt/crowi-plus/node_modules/mongoose/lib/error/validation.js:27:11)
at model.Document.invalidate (/opt/crowi-plus/node_modules/mongoose/lib/document.js:1654:32)
at /opt/crowi-plus/node_modules/mongoose/lib/document.js:1526:17
at Immediate.<anonymous> (/opt/crowi-plus/node_modules/mongoose/lib/schematype.js:785:9)
at runCallback (timers.js:672:20)
at tryOnImmediate (timers.js:645:5)
at processImmediate [as _immediateCallback] (timers.js:617:5)
What is the expected result? (期待される動作)
- Login
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Bug: Creating user data failed after LDAP authentication ...
Anyway, causing 500 is a system bug. I'll fix it whether you succeed configuring the above or not.
Read more >LDAP Authentication error: Login was not successful
When users try to log in to Serv-U client using LDAP Authentication, a home directory is created, however, they get the error message...
Read more >Troubleshooting user login issues with LDAP authentication
This error indicates that LDAP authentication is enabled but the user cannot be authenticated. Do the following: Check the Application Server ...
Read more >Authentication to LDAP fails with AcceptSecurityContext error
The problem is the LDAP is not setup for anonymous binds. To resolve this problem, either change the LDAP to allow anonymous binds,...
Read more >How to Troubleshoot LDAP Authentication - Knowledge Base
The LDAP server is not reachable (check the service routes); User does not exist in LDAP server; Username and/or Password is wrong; Bind...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Mizuho32 Does the user in LDAP have the
uid
attribute ?If not, please set
username
ofAttribute Mapping
in/admin/security
page.Anyway, causing 500 is a system bug. I’ll fix it whether you succeed configuring the above or not.
@Mizuho32 Thank you for your report. I’ll try to reproduce.