UDDI registry security and UDDI registry settings
In addition to the configuration of UDDI registry security, other UDDI registry settings can affect the security of the UDDI registry.
Some UDDI property and policy settings can affect the security of a UDDI registry. Other UDDI settings are not specific to security, but can place restrictions on the successful completion of publish requests.
Security specific considerations
UDDI registry interfaces are protected, as detailed in Access control for UDDI registry interfaces.
The UDDI registry supports the use of XML Digital Signatures to sign UDDI entities. See Use of digital signatures with the UDDI registry.
Some UDDI property and policy settings can affect the security of a UDDI registry. To review or change the following property settings, click UDDI > UDDI Nodes > uddi_node_name .
- 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, see 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 is no longer valid.
- Default user name
- The default user name is used for publish operations when WAS security is disabled and no authentication token data is supplied.
To reset the following policy settings, click UDDI > UDDI Nodes > uddi_node_name > [Policy Groups] API policies.
These policy settings apply when UDDI security features are used and WAS security is enabled. If the UDDI service is mapped to the AllAuthenticatedUsers security role, these settings are overridden. See Set UDDI Security with WAS security enabled.
- Authorization for inquiry
- Whether authorization using authentication tokens is required for inquiry API requests.
- Authorization for publish
- Whether authorization using authentication tokens is required for publish API requests.
- Authorization for custody transfer
- Whether authorization using authentication tokens is required for custody transfer API requests.
Additional considerations
Some UDDI property and keying policy settings influence publish behavior. These settings are not specific to security, but consider them because they place restrictions on the successful completion of publish requests.
To reconfigure the following property settings, click...
.UDDI > UDDI Nodes > uddi_node_name
- Automatically register UDDI publishers
- The UDDI registry requires that publisher entitlements are set before allowing any publish requests. This option automatically registers users with default entitlements.
If this option is not selected, we can register users as UDDI publishers, and specify their entitlements, by using the UDDI publisher settings.
- Use tier limits
- Specifies that publication tier limits are enforced.
If we select this option, one or more tiers must be configured using the UDDI Tier settings. Also, ensure that registered UDDI Publishers are assigned to a tier by using the UDDI publisher settings.
To reset the following property setting, click UDDI > UDDI Nodes > uddi_node_name > [Policy Groups] Keying policies.
- Registry key generation
- If this option is selected, publishers can request key space and, if successful, publish with publisher-assigned keys.
Subtopics
UDDI registry user entitlements
Related concepts
Access control for UDDI registry interfaces
Use of digital signatures with the UDDI registry
Related tasks
Set the UDDI registry to use WAS security
Set UDDI security with WAS security enabled
Set UDDI Security with WAS security disabled
Set UDDI registry security
Related information
UDDI node settings
UDDI node API policy settings
UDDI Publisher settings
Tier collection
UDDI Tier settings
UDDI keying policy settings