github-actions[bot] commented on issue #10386:
URL: 
https://github.com/apache/dolphinscheduler/issues/10386#issuecomment-1150895576

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   When configuring conf/application-api.properties for ldap authentication
   
   ````
   security.authentication.type=LDAP
   ldap.urls=ldap://xx.xx.xx.xx:389
   ldap.base.dn=cn=users,cn=accounts,dc=hadoop,dc=com
   ldap.username=cn=Directory Manager
   ldap.password=xxxx
   ldap.user.identity.attribute=uid
   ldap.user.email.attribute=mail
   ````
   
   
![image](https://user-images.githubusercontent.com/28641261/172813992-8dda359b-798c-40ad-8da5-909b98a692f4.png)
   
   
   ### What you expected to happen
   
   The error is that the user is disabled, query the database to find
   ````
              id: 2
       user_name: user1
   user_password: NULL
       user_type: 1
           email: [email protected]
           phone: NULL
       tenant_id: 0
     create_time: 2022-06-08 11:01:43
     update_time: 2022-06-08 11:01:43
           queue:
           state: 0
   ````
   
   state state is 0
   
   The user state created in the code and read from ladp is 0 by default, so 
after connecting to ladp, users in ladp still cannot log in
   
   
   ### How to reproduce
   
   The operation is as above, the above phenomenon will occur when any ladp is 
configured.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   2.0.5
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to