When you configure HCL Connections portlets to use single sign-on, you might need to
change the Portal realm name to match the one used in HCL Connections.
Procedure
-
In the WebSphere® Application Server Integrated Solutions Console, change
the realm name.
For example, from defaultWIMFileBasedRealm to
AD.cn.ibm.com:389.
- Configure Portal to use the new realm name as the default
realm:
-
Use a text editor to open the wkplc.properties file, which is in the
wp_profile_root/ConfigEngine/properties
directory.
-
For defaultRealmName, type the realmName property value you want to use as the default realm.
- Save your changes to the wkplc.properties file.
-
Run the following task from the wp_profile_root/ConfigEngine directory to set this realm as the default
realm:
./ConfigEngine.sh wp-default-realm -DWasPassword=password
- Stop and restart all necessary servers to propagate
your changes.
-
The default Portal administrator user ID is a file-based user ID, which is unlikely to exist in
your HCL Connections realm. Follow these steps to change
the WAS and Portal administrator user ID to an available user ID in the HCL Connections realm.
-
Run the following command from the wp_profile_root/ConfigEngine directory to replace the existing WebSphere® Application Server administrative user ID and group ID with the new
user and group.
./ConfigEngine.sh wp-change-was-admin-user -DWasPassword=password -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid
Important: You must provide the full distinguished name (DN) for the newAdminId and newAdminGroupId
parameters.
Note: The task is intended to run against a running server. If the server is stopped, add
the -Dskip.ldap.validation=true parameter to the task to skip
the validation.
-
Verify that the task completed successfully. In a clustered environment, restart the deployment
manager, the node agents, and HCL Portal servers. In a
stand-alone environment, restart the server and HCL Portal
servers.
-
Run this task to replace the old HCL Portal
administrative user ID and group ID with the new user and group:
./ConfigEngine.sh wp-change-portal-admin-user -DWasPassword=password -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid
Important: You must provide the full distinguished name (DN) for the newAdminId and newAdminGroupId
parameters.
Note: The task is intended to run against a running server. If the server is stopped, add
the -Dskip.ldap.validation=true parameter to the task to skip
the validation.