IBM E02HRLL-G Administration Guide - Page 82
User names and groups, Stopping the use of LDAP authentication, Notes for UNIX users, Console System
![]() |
View all IBM E02HRLL-G manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 82 highlights
User names and groups Groups provide superuser permissions to all users who are members of the Hubadmin group. By using groups, more than one user can have Hub Administrative responsibilities while maintaining password security. Because unique user names are required on an LDAP server, user names must be unique on WebSphere Partner Gateway as well. If you are creating a new user and the user name already exists in the same or a different partner, you will see an error message stating, A User with this name already exists. In this situation, input another user name into the console and continue. If you are migrating to a new version of WebSphere Partner Gateway wherein there is no restriction on user names, then a double asterisk ** is displayed next to any duplicate user name indicating that it already exists in the same or another partner. Change one of the user names so that they are unique from one another. Note: New users and groups, which are added to the LDAP server and WAS Admin console, must also be added in the WebSphere Partner Gateway console in order to be active. Stopping the use of LDAP authentication You might have to stop LDAP authentication under the following circumstances: v The LDAP server stops or permanently goes down. v Container based authentication was chosen when installing WebSphere Partner Gateway but the LDAP server is not ready. Notes for UNIX users: 1. UNIX users who use DB2 must log in as the db2instance user and use the db2instance username and password to run the script. 2. UNIX users who use Oracle must log in as the oracle user and use the username and password given at the time of installation to run the script. To stop WebSphere Partner Gateway from using LDAP for accessing passwords and instead use the WebSphere Partner Gateway database to store passwords, run the following script: v bcgResetAuthentication.bat for Windows v bcgResetAuthentication.sh for UNIX This script requires the following input parameters: - database schema owner user ID - database schema owner password The script requires these parameters to connect to the WebSphere Partner Gateway database. Note: If you are using a DB2 database, start the script from a DB2 command line. This script is located in the {dbloader install location}/scripts/{database type} directory. This script: v Sets the attribute bcg.ldap.containerauth located in the Console System Administration > Console Properties > Common Attributes to False. 76 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide
![](/manual_guide/products/ibm-e02hrllg-administration-guide-f948001/82.png)