search

HCL-TECH-SOFTWARE / connections-automation

Deployment and upgrade automation scripts for HCL Connections 7.0 based on Ansible
Apache License 2.0
17 stars 31 forks source link

No default value for WAS SSO domain name defined #302

Closed marde16 closed 9 months ago

marde16 commented 11 months ago

There is no default value for variable __sso_domainname

https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/third_party/ibm/wasnd/was-dmgr-config-sso-update/templates/update_sso_config_in_global_security.py.j2#L9

in vars defined.

https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/third_party/ibm/wasnd/was-dmgr-config-sso-update/vars/main.yml#L1-L19

Without this value the 'Domain name' in the WAS SSO Settings is blank and "Users can only log into Profiles (KB0021626)"

marde16 commented 11 months ago

I found the root cause why the 'Domain name' in my environment is blank:

The ansible variable "ansible_domain" of the ansible host is empty.

https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/third_party/ibm/wasnd/was-dmgr-config-sso-update/tasks/create_sso_domainnames.yml#L15-L19

It seems here should be the domain defined via a variable.

-- update --

After I read the documentation again I realized that I forgot to run the post-install playbook.

After the run the post install playbook set the Domain name, but as follows: .;.mydomain.com because the ansible variable "ansible_domain" of the ansible host is empty.

https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/third_party/ibm/wasnd/was-dmgr-config-sso-update/tasks/create_sso_domainnames.yml#L6-L10

It seems we need a differentiation between Single domain SSO with and without ansible_domain.