Changing an administrative security user ID or password

In IBM® Integration Designer, the default administrative security user ID and password is admin unless you chose to change the default user ID and password when you used IBM Installation Manager to install IBM Integration Designer. It is generally recommended that you change the default user ID and password to better secure your test environment servers and business integration applications.

1. If you want to change both the administrative security user ID and the password, complete the following steps in the server administrative console:
   1. If your server is not yet running, right-click your server in the Servers view and select Start.
   2. When the server status changes to Started, right-click the server and select Administration > Run Administrative Console. The administrative console opens.
   3. In the User ID and Password fields, type your default user ID and password and then click Log In.
   4. In the left frame, expand Security and select Secure administration, applications, and infrastructure. The Secure Administration, Applications, and Infrastructure page opens.
   5. Ensure that the Enable administrative security check box is selected.
   6. Click the Security Configuration Wizard button. The Specify Extent of Protection page opens.
   7. Accept the default values and click Next. The Select User Repository page opens.
   8. Accept the default values and click Next. The Configure User Repository page opens.
   9. In the Primary administrative user name field, type the new user ID that you want to use for administrative security.
   10. In the Password and Confirm Password fields, type the password that you want to use for the new administrative security user ID.
   11. Click Next. The Summary page opens.
   12. Click Finish. The Secure Administration, Applications, and Infrastructure page opens again.
   13. Expand Java Authentication and Authorization Service.
   14. Click J2C authentication data. The J2C Authentication Data page opens.
   15. Click the BPC_Auth_Alias link. The BPC_Auth_Alias page opens.
   16. In the User ID and Password fields, type your new administrative security user ID and password.
   17. Click OK. The J2C Authentication Data page opens again.
   18. Using the same technique that you used for BPC_Auth_Alias, specify your new administrative security user ID and password for each of the other aliases listed on the J2C Authentication Data page.
   19. In the left frame, expand Security and select Bus Security. The Bus Security page opens.
   20. Click the BPC.widCell.bus link. The BPC.widCell.bus page opens.
   21. In the bottom right corner of the page, click the Security link. The Security page opens.
   22. Click the Users and groups in the bus connector role link. The Users and Groups in the Bus Connector Role page opens.
   23. Click the New button. The New page opens.
   24. Select the User name radio button.
   25. In the text field beside the User name radio button, type your new administrative user ID.
   26. Click OK. The Users and Groups in the Bus Connector Role page opens again.
   27. Select the check box beside your old administrative security user ID; for example, the user ID admin.
   28. Click Delete.
   29. In the left frame, select Bus Security. The Bus Security page opens again.
   30. Using the same technique that you used for BPC.widCell.bus, specify your new administrative security user ID and delete your old user ID for each of the other buses listed on the Bus Security page.
   31. Click the Save link in the Messages area at the top of the page.
   32. At the top of the administrative console, click Logout and then close the administrative console window.
   33. In the Servers view, right-click your server and select Stop.
2. If you only want to change the password for the administrative security user ID, complete the following steps in the server administrative console:
   1. If your server is not yet running, right-click your server in the Servers view and select Start.
   2. When the server status changes to Started, right-click the server and select Administration > Run Administrative Console. The administrative console opens.
   3. In the User ID and Password fields, type your default user ID and password and then click Log In.
   4. In the left frame, expand Security and select Secure administration, applications, and infrastructure. The Secure Administration, Applications, and Infrastructure page opens.
   5. Ensure that the Enable administrative security check box is selected.
   6. In the Available realm definitions section at the bottom of the page, ensure that Federated repositories is selected and then click Configure. The Federated Repositories page opens.
   7. At the bottom of the page, click Apply. The Administrative User Password page opens.
   8. In the Password and Confirm Password fields, type the new password that you want to use for the administrative security user ID.
   9. Click OK. The Federated Repositories page opens again.
   10. In the left frame, select Secure administration, applications, and infrastructure. The Secure Administration, Applications, and Infrastructure page opens again.
   11. Expand Java Authentication and Authorization Service.
   12. Click J2C authentication data. The J2C Authentication Data page opens.
   13. Click the BPC_Auth_Alias link. The BPC_Auth_Alias page opens.
   14. In the Password field, type your new password for the administrative security user ID.
   15. Click OK. The J2C Authentication Data page opens again.
   16. Using the same technique that you used for BPC_Auth_Alias, specify your new password for each of the other aliases listed on the J2C Authentication Data page.
   17. Click the Save link in the Messages area at the top of the page.
   18. At the top of the administrative console, click Logout and then close the administrative console window.
   19. In the Servers view, right-click your server and select Stop.
3. If you want to update an IBM Integration Designer server configuration to reflect the changes that you made to the administrative security user ID or password in the server administrative console, and you want to update the server configuration in both your current workspace and in all other existing and future workspaces (recommended), then complete the following steps:
   1. From the Window menu, select Preferences. The Preferences window opens.
   2. In the left frame, expand Server and select Security. The Security page opens.
   3. Ensure that the Enable workbench-scoped configuration check box is selected.
   4. In the User ID or Password fields of the server for which you changed the user ID or password in the administrative console, type the same user ID or password that you specified in the administrative console.
   5. Click OK to close the Preferences window. When you next start the server in the Servers view, the new user ID or password will be in effect.
4. If you want to update an IBM Integration Designer server configuration to reflect the changes that you made to the administrative security user ID or password in the server administrative console, but you only want to update the server configuration in your current workspace and not in all other existing and future workspaces, then complete the following steps:
   1. From the Window menu, select Preferences. The Preferences window opens.
   2. In the left frame, expand Server and select Security. The Security page opens.
   3. Clear the Enable workbench-scoped configuration check box.
   4. Click OK to close the Preferences window.
   5. In the Servers view, double-click your server. The server configuration editor opens.
   6. Expand the Servers section.
   7. In the User ID field or Password field, type the same user ID or password that you specified in the administrative console.
   8. Press Ctrl-S to save your changes and then close the server configuration editor. When you next start the server in the Servers view, the new user ID or password will be in effect.
   Information about the pros and cons of using a workbench-scoped security configuration is found in the topic "Enabling or disabling workbench-scoped security configuration."