Pale Rider 9/4 15:05:53 wds.linkis.ldap.proxy.userNameFormat= Pale Rider 9/4 15:06:54 Does anyone have experience with LDAP integration? How should this configuration be set?
Pale Rider 9/4 15:07:07 [grinning face] Mo Xi Zhi Mo 9/4 16:14:04 [image] Mo Xi Zhi Mo 9/4 16:14:56 Normally, if your LDAP service is deployed correctly, configuring these two settings should be sufficient. Pale Rider 9/4 16:15:21 I'm using FreeIPA for LDAP. Pale Rider 9/4 16:15:32 But even after filling in these two settings, it's still not working. Mo Xi Zhi Mo 9/4 16:17:18 What did you configure for the domain? Pale Rider 9/4 16:18:10 Something like this. Pale Rider 9/4 16:18:10 [image] Pale Rider 9/4 16:28:13 ] o.a.l.g.s.LDAPUserRestful (30) [apply] [JobId-] - wrong user name or password! javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials] Mo Xi Zhi Mo 9/4 16:38:58 You can paste this error into a large language model and ask. It's likely that your DN configuration is incorrect or the password is wrong. First, verify using a tool like ldapwhoami. Pale Rider 9/5 09:02:10 With the proxy mode like wds.linkis.gateway.conf.enable.proxy.user=true, can one user proxy all users in a Kerberos environment? Pale Rider 9/5 09:12:10 [image] Pale Rider 9/5 09:12:28 I can query using User A, but when using User B, the query returns this error. Mo Xi Zhi Mo 9/5 10:09:59 This doesn't seem related to the proxy. Please clear the data according to the guidelines. Pale Rider 9/5 10:11:45 Which data should I clear? Mo Xi Zhi Mo 9/5 10:21:44 Check the backend logs and paste the error stack trace. Pale Rider 9/16 15:19:58 RemoteException: User: [email protected] is not allowed to impersonate dbquery
