Taxonomic Classifications Basic Concepts of the UDDI Specification

1.3.3. Security Considerations

UDDI specification does not define an access control mechanism. The UDDI specification allows modification of the specific entity only by its owner creator. This does not scale in the enterprise environment where the right to modify or delete a specific UDDI entity must be assigned with more identities or even better with some role. Oracle Service Registry addresses this issue with the ACL Access Control List extension to the UDDI security model. Every UDDI entity can be associated with the ACL that defines who can find list it in some UDDI query result, get retrieve all details of the UDDI object, modify or delete it. The ACL can reference either the specific user account or user group. The UDDI v3 specification provides support for digital signatures. In Oracle Service Registry, the publisher of a UDDI structure can digitally sign that structure. The digital signature can be validated to verify the information is unmodified by any means and confirm the publishers identity.

1.3.4. Notification and Subscription

The UDDI v3 specification introduces notification and subscription features. Any UDDI registry user can subscribe to a set of UDDI entities and monitor their creation, modification and deletion. The subscription is defined using standard UDDI get or find API calls. The UDDI registry notifies the user whenever any entity that matches the subscription query changes even if the change causes the entity to not match the query anymore. It also notifies about entities that were changed in a way that after the change they match the subscription query. The notification might be synchronous or asynchronous. By synchronous, we mean solicited notification when the interested party explicitly asks for all changes that have happened since the last notification. Asynchronous notifications are run periodically in a configurable interval and the interested party is notified whenever the matched entity is created, modified, or deleted.

1.3.5. Replication

Content of the UDDI registry can be replicated using the simple master-slave model. The UDDI registry can replicate data according to multiple replication definitions that are defined using UDDI standard queries. The master-slave relationship is specific to the replication definition. So one registry might be master for one specific replication definition and slave for another. The security settings ACL, users, and groups are not subject to replication but you can set permissions on replicated data.

1.3.6. UDDI APIs

The core data management tools functions of a UDDI registry are: • Publishing information about a service to a registry. • Searching a UDDI registry for information about a service. The UDDI specification also includes concepts of: • Replicating and transferring custody of data about a service. • Registration key generation and management. • Registration subscription API set. • Security and authorization. The UDDI specification divides these functions into Node API sets that are supported by a UDDI server and Client API Sets that are supported by a UDDI client . Page 157

1.3.6. UDDI APIs

1.3.7. Technical Notes

Technical Notes TN are non-normative documents accompanying the UDDI Specification that provide guidance on how to use UDDI registries. Technical Notes can be found at http:www.oasis-open.orgcommitteesuddi-specdoctns.htm . One of the most important TNs is Using WSDL in a UDDI Registry.

1.3.8. Benefits of UDDI Version 3

The most important features include: • User-friendly identifiers facilitate reuse of service descriptions among registries. • Support for digital signatures allows UDDI to deliver a higher degree of data integrity and authenticity. • Extended discovery features can combine previous, multi-step queries into a single-step, complex query. UDDI now also provides the ability to nest sub-queries within a single query, letting clients narrow their searches much more efficiently.

1.4. Subscriptions in Oracle Service Registry

Subscriptions are used to alert interested users in changes made to structures in Oracle Service Registry. The Oracle Service Registry Subscription API provides users the ability to manage save and delete subscriptions and evaluate notification. Notifications are lists of changes made within a specified time interval. The Subscription mechanism allows the user to monitor new, changed, and deleted entries for businessEntities, businessServices, bindingTemplates, tModels or publisherAssertions. The set of entities in which a user is interested is expressed by a SubscriptionFilter, which can be any one of the following UDDI v3 API queries: • find_business , find_relatedBusinesses, find_services, find_bindings, find_tmodel • get_businessDetail , get_serviceDetail, get_bindingDetail, get_tModelDetail, get_assertionStatusReport Note In Business Service Control, users can also create subscriptions also resources WSDL, XML, XSD and XSLT without a detailed knowledge of how resources are mapped to UDDI data structures.

1.4.1. Subscription Arguments

A subscription is the subscribers interest in changes made to entities as defined by the following arguments: • SubscriptionKey - The identifier of the subscription, as generated by the server when the subscription is registered. • Subscription Filter - Specifies the set of entities in which the user is interested. This field is required. Note that once the subscription filter is set, it cannot be changed. • Expires After - The time after which the subscription is invalid optional. • Notification Interval - How often the client will be notified optional. The server can extend it to the minimum supported notification interval supported by the server as configured by the administrator. For more information, please see Administrators Guide, Section 2, Registry Configuration . • Max Entities - how many entities can be listed in a notification optional. When the number of entities in a notification exceeds max entities, the notification will contain only the number of entities specified here or in the registry configuration. A chunkToken different from 0 will be specified in the notification. This chunkToken can be used to retrieve trailing entities. Page 158

1.4.1. Subscription Arguments