UDDI Registry security additional considerations
In addition to the configuration of UDDI Registry security, there a number of other UDDI Registry settings which may affect the behavior of the UDDI Registry. Some of these settings are security specific, others are points to bear in mind when configuring security.
Additional security considerations
The UDDI Registry also supports use of XML Digital Signatures to sign UDDI entities. This is described in Use of digital signatures with the UDDI Registry.
Additional policy considerations
A number of the UDDI property and policy settings also determine the behavior of a UDDI Registry with respect to security.
To review or change the following property settings, click UDDI > UDDI Nodes > uddi_node. The settings are also detailed in the administrative console help.
- Key space requests require digital signature
- This setting determines whether all tModel:keyGenerator requests for key space must be digitally signed. To understand key space refer to UDDI Registry V3 Entity Keys.
- Use authInfo credentials if provided
- This setting applies only when WAS security is disabled. See Configuring UDDI Security with WAS security disabled.
- Authentication token expiry period
- The authentication token expiry period is the length of idle time (in minutes) allowed before an authentication token becomes invalid.
- Default user name
- The default user name is used for publish operations when WebSphere Application Server security is disabled and no authentication token data is supplied.
To review or change the following policy settings, click UDDI > UDDI Nodes > uddi_node, and under Policy Groups, click APIs. The settings are also detailed in the administrative console help.
The above policy settings apply when UDDI security features are being used. If WAS security is enabled and the UDDI service in question is mapped to the security role AllAuthenticatedUsers, these settings will be overridden. See Configuring UDDI Security with WebSphere Application Server security enabled and Configuring UDDI Security with WAS security disabled.
- Authorization for inquiry
- Specifies whether authorization using authentication tokens is required for inquiry API requests.
- Authorization for publish
- Specifies whether authorization using authentication tokens is required for publish API requests.
- Authorization for custody transfer
- Specifies whether authorization using authentication tokens is required for custody transfer API requests.
Other considerations
In addition to the property and policy settings above, be aware that some UDDI keying and user policy settings also influence publish behavior. These settings are not specific to security, but you should bear them in mind as they also place restrictions on successful completion of publish requests.
To review or change the following property settings, click UDDI > UDDI Nodes > uddi_node. The settings are also detailed in the administrative console help
- Automatically register UDDI publishers
- The UDDI Registry requires publisher entitlements to be set before allowing any publish requests. This option automatically registers users with default entitlements.
If this option is not selected, users (and their entitlements) can be registered. See UDDI Publisher settings.
- Use tier limits
- If selected, tier limits are enforced.
If this option is selected you should have one or more tiers configured (see Tier collection and UDDI Tier settings). You should also ensure that registered UDDI Publishers are assigned to a tier (see UDDI Publisher settings).
To review or change the following property setting, click UDDI > UDDI Nodes > uddi_node, and under Policy Groups click UDDI Keying. The setting is also detailed in the administrative console help.
- Registry key generation
- If this option is selected, publishers may request key space and, if successful, publish with publisher assigned keys.
Related Tasks
Configuring the UDDI Registry to use WAS security
Configuring the UDDI Registry to use UDDI security