+

Search Tips   |   Advanced Search

 

Configure UDDI Security with WAS security enabled

 

To configure UDDI security, you can use the UDDI V3 security API or the UDDI V1 and V2 publish security features. Because WAS security is enabled, WebSphere Application Server data confidentiality management is independent of UDDI security.

 

Overview

When WAS security is enabled, use the console to complete the following steps:

 

Procedure

  1. In the navigation pane, click Applications > Enterprise Applications.

  2. In the content pane, click the UDDI registry application. Under Detail Properties click Security role to user/group mapping.

  3. Set the WAS security role mappings to Everyone for the following UDDI services:

    • Versions 1 and 2 SOAP publish service (SOAP_Publish _User)

    • V3 publish service (V3SOAP_Publish_User_Role)

    • V3 custody transfer service (V3SOAP_CustodyTransfer_User_Role)

    • V3 security service (V3SOAP_Security_User_Role)

    Changing the role mappings to Everyone prevents WebSphere Application Server security from overriding UDDI security.

  4. Ensure that UDDI Policy is set to require the use of authentication tokens for the UDDI V3 Publish and Custody Transfer services (use of authentication tokens is already required for V1 and V2 Publish services). To do this, click UDDI > UDDI Nodes > uddi_node_name, and under Policy Groups click API policies. Select the Authorization for publish and Authorization for custody transfer check boxes. (Select the Authorization for inquiry check box if you require authentication for UDDI Inquiry services).

  5. Click OK.

 

Results

With this configuration, no Security Role authentication restriction is imposed, but the credentials (user name and password) associated with the authentication token are authenticated by WAS.

When WAS security is enabled, WAS data confidentiality management is independent of UDDI security and is managed as described in Configure the UDDI registry to use WAS security.


Next topic: UDDI registry security additional considerations

 

Related tasks


Configure UDDI Security with WAS security disabled
Configure the UDDI registry to use UDDI security

 

Related Reference


Security API for the UDDI V3 registry