Configure the UDDI Registry to use WebSphere Application Server security
Configure the UDDI Registry to use WebSphere Application Server security
Before starting this task complete the following two steps:
Enable WebSphere Application Server global security (see Configuring global security). This will allow the UDDI Registry to exploit the WebSphere Application Server security features.
Ensure that WebSphere Application Server is configured to use HTTPS (SSL);
this will allow the use of secure access with the UDDI Registry. WebSphere Application Server is configured by default to accept SSL requests on port 9443, however if you need to make any additional SSL configuration changes,
please refer to Secure Sockets Layer settings for custom properties.
There are two aspects of WebSphere Application Server security which are exploited by the UDDI registry:
Authorization
Authorization determines whether users are allowed access to services.
WebSphere Application Server determines authorization by mapping users, or groups of users, to roles. UDDI makes use of two WebSphere Application Server special subjects: Everyone (all users are allowed access) and AllAuthenticatedUsers (only valid WebSphere Application Server registered users are allowed access).
Data confidentiality
Data confidentiality determines security at the transport level. Data confidentiality for WebSphere Application Server services can be either 'none'
(HTTP is used as the transport protocol) or 'confidential' (requiring the use of SSL; HTTPS is used as the transport protocol).
When WebSphere Application Server security is enabled,
the default settings in the UDDI Version 3 Application and Web deployment descriptors result in the following features:
Publish, Custody Transfer and Security services are mapped to the AllAuthenticatedUsers special subject, and data confidentiality is enforced (HTTPS is used). Authentication uses the standard WebSphere Application Server security facilities and there is no separate registration function for the UDDI registry. To use publish functions, users must supply their WebSphere Application Server user name and password (unless you have modified the supplied publish role), and must also be registered UDDI Publishers. By registering users as UDDI Publishers you control which users in the AllAuthenticatedUsers subject can update the UDDI Registry.
Inquiry services are mapped to the Everyone special subject, and data confidentiality is not enforced (HTTP is used). To use inquiry services, users do not need to supply a user name or password, and do not have to be registered UDDI publishers.
You are recommended to use the default settings as described above.
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.
To change the default settings follow the steps below:
To change the role mappings using the administrative console, complete the following steps:
In the navigation pane, click
Applications
> Enterprise Applications .
In the content pane, click the UDDI Registry application.
Under Additional Properties on the right hand side, click Map security roles to users/groups .
Make any changes you require and click OK .
To change the role mappings using the wsadmin command, complete the following steps:
Use the MapRolesToUsers option of the edit command of the AdminApp object to map the roles defined in the UDDI Registry application to special subjects (Everyone or AllAuthenticatedUsers), to users, or to user groups.
For example, the following JACL statement maps the Version 3 GUI Publish role to Everyone, and the Version 3 SOAP Publish role to user 'user1' and group 'group1':
$AdminApp edit $AppName {-MapRolesToUsers { {"GUI_Publish_User" Yes No "" ""} {"V3SOAP_Publish_User_Role" No No "user1" "group1"} }}
where $AppName 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.