Configuring the Dynamic Workload Console to use the local OS or PAM authentication method
About this task
To modify the Dynamic Workload Console authentication method to use the local OS or PAM authentication method, perform the following steps:
Procedure
- Log in to the Dynamic Workload Console with WebSphere Application Server administration credentials.
- From the navigation toolbar, click the search glass icon, on top of the toolbar. In the search field, enter WebSphere Administrative Console to open the administrative console.
- Click Launch WebSphere administrative console.
- From the administrative console navigation tree, click Users and Groups > Manage users to create a new user on the file registry (do not create it on the operating system).
- Switch back to the Dynamic Workload Console.
- From the navigation toolbar, click the search glass icon, on top of the toolbar. In the search field, enter User Roles to open the User Roles page.
- Enter the new user account in the User ID field and click Search.
- Click on the user name in the results table.
- Select the roles the for primary administrative user. Usually all roles are assigned.
- Press the Save button.
- Backup the WebSphere Application Server configuration using the backupConfig command.
- Dump your current security properties to a text file by
using the following command:
showSecurityProperties.sh > text_file
- Customize the security properties by editing the file as
follows: Note: If you want to use PAM authentication, specify the following property in the file activeUserRegistry=Custom.
################################################################ Global Security Panel ################################################################ enabled=true enforceJava2Security=false useDomainQualifiedUserNames=false cacheTimeout=600 ltpaTimeOut=720 issuePermissionWarning=false activeProtocol=CSI useFIPS=false activeAuthMechanism=LTPA activeUserRegistry=LocalOS ################################################################ Federated Repository Panel ################################################################ PrimaryAdminId=new_user UseRegistryServerId=true ServerID=new_user ServerPassword=new_pwd VMMRealm=TWSREALM VMMRealmDelimiter=@ VMMIgnoreCase=true
- Stop the server by using the stopWas.sh wastool. To stop the server, use the WebSphere Application Server administration credentials.
- Load the new properties by entering the following command:
complete_path/changeSecurityProperties.sh text_file
- Restart the server by using the startWas.sh wastool.