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
Installing CP4BA only selecting ODM and the optional tools.
Install failing at gitea section where it attempts to sync LDAP users and fails to authenticate with the LDAP service.
We tested that the LDAP service was available and logged in using the cpadmin DN and the generated universal_password found in the logs. Proving LDAP and the credentials were valid. Example password __omit_place_holder__dc91d9ecca04b38c3cfa2a1873f305495e4eaae1
With increased logging -vvvvvv we then saw that the password being used for Basic Auth was null.
Specifying a strong password on the cmd line resolved this issue.
./cp-deploy.sh env apply --skip-infra --accept-all-licenses -v -e universal_password=
Conclusion is that something in that code section is not accepting the universal_password when auto generated, perhaps due to length as it is over 60 chars and it then reverts to using null causing the issue authenticating to LDAP.
Is the universal_password being generated incorrectly with omit_place_holder that then makes it too long?
The text was updated successfully, but these errors were encountered:
Installing CP4BA only selecting ODM and the optional tools.
Install failing at gitea section where it attempts to sync LDAP users and fails to authenticate with the LDAP service.
Link to slack thread on the issue and fix
We tested that the LDAP service was available and logged in using the cpadmin DN and the generated universal_password found in the logs. Proving LDAP and the credentials were valid. Example password __omit_place_holder__dc91d9ecca04b38c3cfa2a1873f305495e4eaae1
With increased logging -vvvvvv we then saw that the password being used for Basic Auth was null.
Specifying a strong password on the cmd line resolved this issue.
./cp-deploy.sh env apply --skip-infra --accept-all-licenses -v -e universal_password=
Conclusion is that something in that code section is not accepting the universal_password when auto generated, perhaps due to length as it is over 60 chars and it then reverts to using null causing the issue authenticating to LDAP.
Is the universal_password being generated incorrectly with omit_place_holder that then makes it too long?
The text was updated successfully, but these errors were encountered: