universal_password must be specified at install
Maintainers usually reply within 1 day
@jandusek4 is already working on this.
Since Sep 18, 2024.
Assessment
This issue has not been assessed yet.
Description
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.
TASK [gitea : Sync LDAP Users] *************************************************
Wednesday 21 June 2023 12:20:07 +0000 (0:01:20.759) 0:08:27.103 ********
fatal: [localhost]: FAILED! => {"cache_control": "no-store, no-transform", "changed": false, "connection": "close", "content_length": "146", "content_type": "application/json;charset=utf-8", "date": "Wed, 21 Jun 2023 12:20:14 GMT", "elapsed": 6, "json": {"message": "token is required", "url": "https://gitea.pluto-01-f7d2a3e582d10670c7df1a3b36d5b194-0000.eu-de.containers.appdomain.cloud/api/swagger"}, "msg": "Status code was 401 and not [204]: HTTP Error 401: Unauthorized", "redirected": false, "set_cookie": "10e73728790f636df27fadfad33f18b0=ca831b395a91565b3e753f9e92f91e56; path=/; HttpOnly; Secure; SameSite=None", "status": 401, "url": "https://gitea.pluto-01-f7d2a3e582d10670c7df1a3b36d5b194-0000.eu-de.containers.appdomain.cloud/api/v1/admin/cron/sync_external_users", "x_content_type_options": "nosniff", "x_frame_options": "SAMEORIGIN"}
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?
- Dominant language
- Jinja
- Stars
- 163
- Forks
- 82
- Avg merge
- 6m
- Merged PRs (30d)
- 12
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IBM/cloud-pak-deployer
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
IBM/cloud-pak-deployer#1205 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
IBM/cloud-pak-deployer#1160 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IBM/cloud-pak-deployer#1152 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
IBM/cloud-pak-deployer#1143 ·
Maintainers usually reply within 1 day
-
Deploy IBM bob using deployerPossibly taken @thomas-mattsson claimed this 14 days ago. Open
IBM/cloud-pak-deployer#1195 · 1 comment · 2 reactions · 1 assignee ·
Maintainers usually reply within 1 day