Customize login attributes
By default, Profiles looks at the login table and the three login attributes defined below to perform. To improve performance, you can comment out the attributes that are not used in your environment.
Before starting
To edit configuration files, use the wsadmin client. See Starting the wsadmin client for information about how to start the wsadmin command-line tool.
About this task
Default mappings for uid and mail are provided. To use a mapping for loginId, replace ADMIN_REPLACE in the loginField element with the appropriate login attribute specified in WAS. This section should only contain those login attributes that will be used in a deployment. For example, if users only log in with email, then the mappings for uid and loginId should be commented out or removed.For more information on enabling and disabling access to profiles, see Forcing users to log in before they can access an application.
Procedure
- From the dmgr host:
cd $DMGR_PROFILE/bin
./wsadmin.sh -jython
execfile("profilesAdmin.py")If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored.
- Check out the Profiles configuration files:
ProfilesConfigService.checkOutConfig("<working_directory>", "<cell_name>")where:
- <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes (/) to separate directories in the file path, even if you are using the Microsoft Windows operating system.
Note: AIX and Linux only: The directory must grant write permissions or the command does not complete successfully.
- <cell_name> is the name of the WAS cell hosting the Profiles application. This argument is required. It is also case-sensitive, so type it with care. If you do not know the cell name, you can determine it by typing the following command in the wsadmin command processor: print AdminControl.getCell()
For example:
- AIX or Linux:
ProfilesConfigService.checkOutConfig("/opt/prof/temp","foo01Cell01")
- Microsoft Windows:
ProfilesConfigService.checkOutConfig("c:/prof/temp","foo01Cell01")
Locate the Profiles configuration file, profiles-config.xml, in the local working directory specified in the checkOutConfig command. The Profiles configuration file contains the various configuration settings for the Profiles application. Here is the relevant section of the file that is used for customizing login attributes:
<loginAttributes> <loginAttribute>uid</loginAttribute> <loginAttribute>email</loginAttribute> <loginAttribute>loginId</loginAttribute> </loginAttributes>
Comment out any attributes that are not used in your environment.
For example:
<loginAttributes> <loginAttribute>uid</loginAttribute> <! -- The following login attribute is not used <loginAttribute>email</loginAttribute> --> <loginAttribute>loginId</loginAttribute> </loginAttributes>
After making changes, check the configuration files back in, and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Apply property changes in Profiles for information about how to save and apply your changes.
Parent topic
Customize the Profiles user interface
Related tasks
Apply property changes in Profiles
Forcing users to log in before they can access an application
});