Before you begin
Before starting this task complete the following two steps:Why and when to perform this task
With the UDDI roles mapped to either the Everyone class or the AllAuthenticatedUsers class, you can then control which individual users in those classes can update the UDDI Registry by registering those users as UDDI publishers. This is the recommended course of action. However, you can change the defaults by mapping roles to different users or user groups, or by not mapping a role to any users or user groups, in which case all access to that role will be disabled. If you do map roles to users or groups, turn on the Automatically register UDDI publishers property (see UDDI node settings) so that you do not have to use two mechanisms for giving access to a subset of users.
For more information about UDDI role mappings, and a list of UDDI Registry services and roles, see Access control for UDDI Registry interfaces.
To change the default settings follow the steps below:
Steps for this task
$AdminApp edit $AppName {-MapRolesToUsers { {"GUI_Inquiry_User" Yes No "" ""} {"V3SOAP_Publish_User_Role" No Yes "" ""} }}where $AdminApp is a variable representing the name of the UDDI Registry application.
For more information about using the MapRolesToUsers option, see Options for the AdminApp object install, installInteractive, edit, editInteractive, update, and updateInteractive commands.
Related concepts
Access control for UDDI Registry interfaces
Related tasks
Configuring the UDDI Registry to use UDDI security
Configuring SOAP API and GUI services
Related reference
Options for the AdminApp object install, installInteractive, edit,
editInteractive, update, and updateInteractive commands