-
Notifications
You must be signed in to change notification settings - Fork 469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing or Incorrect Authentication Configuration for ldap_user in ClickHouse #1630
Comments
could you share |
@Slach ClickHouse Installation Manifest
|
@Slach did you find anything from CHI. |
@Slach I have made one changes in CHI by adding one more section, now pod is not crashing by above error but still not getting authenticated
Do i need follow any more step line to create user locally..? Even i have added one user like which is in AD CREATE USER 'sanjeev.gautam-a' IDENTIFIED WITH ldap SERVER 'my_ldap_server'; Even verified using ldapsearch getting detail for this user using mentioned ldap details.
|
@Slach did you get any thing based on shared details..? |
unfortunatelly have not time to deep figure out, i'm not expert with ldap |
An error occurs when parsing the ldap_user configuration in the ClickHouse users.xml file. The error indicates that an authentication method is not properly specified for the user, even though the configuration appears to include the required ldap authentication type.
Error Details:
Error: Application: Code: 36. DB::Exception: Either 'password' or 'password_sha256_hex' or 'password_double_sha1_hex' or 'no_password' or 'ldap' or 'kerberos' or 'ssl_certificates' or 'ssh_keys' or 'http_authentication' must be specified for user ldap_user.: while parsing user 'ldap_user' in users configuration file: while loading configuration file '/etc/clickhouse-server/users.xml'. (BAD_ARGUMENTS)
ldap_user in the users.xml
LDAP server configuration is defined in 04-ldap-config.xml:
Expected Behavior:
The ClickHouse server should start without errors, and the ldap_user should authenticate using the specified LDAP server configuration.
The text was updated successfully, but these errors were encountered: