Configure UDDI Security with WAS security disabled
Overview
With WAS security disabled, neither WAS security roles nor data confidentiality constraints apply. This mode may be useful for test UDDI Registry configurations.
In this mode, UDDI V1 and V2 security features are active:
- UDDI V1 and V2 publish requests require UDDI V1 and V2 authentication tokens respectively. Publishers requesting or using an authentication token must be registered WAS users.
- UDDI V1 and V2 inquiry requests do not require authentication tokens.
No further configuration is required for UDDI V1 and Version 2 security.
For UDDI V3, the use of the UDDI V3 Security API, and the use of authentication tokens with V3 Publish and Custody Transfer APIs, is optional. To make use of these UDDI V3 security features, use the administrative console to complete the following steps:
Procedure
- Specify that use of authInfo is required: click UDDI > UDDI Nodes > uddi_node. In the General Properties section select the Use authInfo credentials if provided check box.
- Ensure that UDDI Policy is set to require the use of authentication tokens for the UDDI Publish and Custody Transfer services: click UDDI > UDDI Nodes > uddi_node, and under Policy Groups click APIs. 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).
Related Tasks
Configuring UDDI Security with WAS security enabled
See Also
Security API for the UDDI V3 Registry