You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We tried to configure the bindDn and bindPassword using secrets as shown here for control center. However it doesn't work as expected. When we configure the bindDn and bindPassword in-line (as shown here) it works as expected.
Upon further investigation, we noticed that the jaas-config.file on the pod is malformed when the configuration is via secrets. See below (the bindDn appears to have a double quote at the beginning of the line)
Our environment is on GCP. We tried to replicate this locally on a minikube using the exact same configuration, but the jaas-config.file rendered correctly on minikube. So wondering if this could be a bug specific to a particular platform?
The text was updated successfully, but these errors were encountered:
cijujoseph
changed the title
LDAP authentication into control center not working when bindDn and password are configured using secrets
LDAP authentication into control center not working when bindDn and bindPassword are configured using secrets
Sep 8, 2023
The lda-credential secret, since it was created from a file from a windows machine, it had a carriage return (\r) in it which was causing the bindDn to get substituted incorrectly. It would be good to get that handled in the operator so others won’t run into such issues in the future.
The command kubectl get configmap controlcenter-shared-config showed the following in the output which helped us figure this out.
We tried to configure the
bindDn
andbindPassword
using secrets as shown here for control center. However it doesn't work as expected. When we configure thebindDn
andbindPassword
in-line (as shown here) it works as expected.Upon further investigation, we noticed that the jaas-config.file on the pod is malformed when the configuration is via secrets. See below (the
bindDn
appears to have a double quote at the beginning of the line)Our environment is on GCP. We tried to replicate this locally on a minikube using the exact same configuration, but the jaas-config.file rendered correctly on minikube. So wondering if this could be a bug specific to a particular platform?
The text was updated successfully, but these errors were encountered: