Closed hunqba closed 6 months ago
Hi @hunqba, yes, dashes are not part of standard ENV var naming convention and when you try to print or list env var from bash command line they are not showing. But it should still be working and recognized by startup setup process.
You can find resolved configuration by either set PLATFORM_STARTUP_LOG_LEVEL=DEBUG
then look at startup logs OR simply by cat the file /var/conduktor/configs/config.yml
You can also remove the dash from ENV var like CDK_SSO_LDAP_0_SEARCHSUBTREE
that also should be recognized as valid.
We will try to improve configuration and specially resolve this kind of issue in future.
Hope this help.
I can sign in with LDAP successfully. Thanks @qboileau
I can sign in with LDAP successful. Note that: We need to ensure User email (The only mandatory field) to be configured on AD. https://docs.conduktor.io/platform/get-started/configuration/user-authentication/SSO/ldap/ Thanks @qboileau
Seem like ENV variables contain hyphens or dashes - wasn't accepted. I cannot find any ENV vars named with hyphens in my conduktor-platform pod. Example: LDAP env - refer to: https://docs.conduktor.io/platform/get-started/configuration/user-authentication/SSO/ldap/