Pre-installed Groups Data Access Control: Principles

systemintranet Holds users who access Oracle Service Registry via a local intranet. This group is reserved for a future release. There is no implementation behind it as of Oracle Service Registry 11.1.1

5.1.5. ACL tModels

ACL permissions are represented as tModels as detailed below: v2 tModelKey v3 tModelKey ACL Permission uuid:aacfc8e0-dcf5-11d5-b238-cbbeaea0a8d4 uddi:systinet.com:acl:find-allowed find allowed uuid:ced3c160-dcf5-11d5-b238-cbbeaea0a8d4 uddi:systinet.com:acl:find-denied find denied uuid:f9977a90-dcf5-11d5-b238-cbbeaea0a8d4 uddi:systinet.com:acl:get-allowed get allowed uuid:09e202d0-dcf6-11d5-b238-cbbeaea0a8d4 uddi:systinet.com:acl:get-denied get denied uuid:19885bd0-dcf6-11d5-b239-cbbeaea0a8d4 uddi:systinet.com:acl:save-allowed save allowed uuid:2a25e610-dcf6-11d5-b239-cbbeaea0a8d4 uddi:systinet.com:acl:save-denied save denied uuid:37f44ac0-dcf6-11d5-b239-cbbeaea0a8d4 uddi:systinet.com:acl:delete-allowed delete allowed uuid:4e51d8f0-dcf6-11d5-b239-cbbeaea0a8d4 uddi:systinet.com:acl:delete-denied delete denied uuid:5bc32980-dcf6-11d5-b239-cbbeaea0a8d4 uddi:systinet.com:acl:create-allowed create allowed uuid:6d0be7e0-dcf6-11d5-b239-cbbeaea0a8d4 uddi:systinet.com:acl:create-denied create denied

5.1.6. Setting ACLs on UDDI v3 Structures

In UDDI v3, explicit ACL permission is saved in a special keyedReferenceGroup having the tModelKey uddi:systinet.com:acl . This keyedReferenceGroup can contain only keyedReferences to ACL tModels. Only the terms user and group are allowed in the included keyName, and the keyValue must contain the name of the user or group according to keyName value. For example, user demo_john can save update following businessEntity even if he is not the owner: Example 1. Setting ACLs - v3 businessEntity xmlns=urn:uddi-org:api_v3 ... categoryBag ... keyedReferenceGroup tModelKey=uddi:systinet.com:acl keyedReference tModelKey=uddi:systinet.com:acl:save-allowed keyName=user keyValue=demo_john ... keyedReferenceGroup categoryBag businessEntity

5.1.7. Setting ACLs on UDDI v1v2 Structures

Under versions 1 and 2 of UDDI, explicit ACL permission is saved as a special keyedReference in the categoryBag. This keyedReference refers to one of the tModels representing ACL permissions. Only the terms user and group are allowed in the included keyName and the keyValue must contain the name of the user or group according to the keyName value. Page 208

5.1.7. Setting ACLs on UDDI v1v2 Structures

For example, user demo_john can save update following businessEntity even if he is not the owner: businessEntity ... ... categoryBag keyedReference tModelKey=uuid:19885bd0-dcf6-11d5-b239-cbbeaea0a8d4 keyName=user keyValue=demo_john ... categoryBag businessEntity Note ACL permissions cannot be set on the bindingTemplate structure because this structure has no categoryBag in UDDI v1v2.

5.2. Publisher-Assigned Keys

Under UDDI v1 and v2, keys are generated automatically when a structure is published. Generated keys in these versions are in form uuid:8-4-4-4-12 where the numbers indicate a count of hexadecimal values. For example, uuid:327A56F0- 3299-4461-BC23-5CD513E95C55 . Note that the prefix uuid: was only used in tModelKeys. In UDDI v3 users may assign keys when saving a structure for the first time. These Keys can be 255 characters long and can contain numbers and Latin characters, so that the key itself describes what the UDDI structure means. For example, the key uddi:systinet.com:uddiRegistry:demo:businessService has the following elements: • The prefix uddi: is a schema much like http: or ftp: and must be always present. • systinet.com is an optional host name. • The elements uddiRegistry, demo, and businessService represent a hierarchy of domains. The domain demo is a subdomain of uddiRegistry. This description is sufficient for our purposes for now. For a more precise description of keys, please see the UDDI v3 Specification [http:uddi.orgpubsuddi-v3.00-published-20020719.htm_Toc42047261].

5.2.1. Generating Keys

The key generator tModel is a tModel with a key in the form domain:keygenerator. This tModel permits its owner to save structures with keys in the form domain:string . For example, the tModel uddi:systinet.com:uddiRegistry:demo:keygenerator allows its owner to publish structures with keys like: • uddi:systinet.com:uddiRegistry:demo:businessService • uddi:systinet.com:uddiRegistry:demo:b52 These are derived keys of the uddi:systinet.com:uddiRegistry:demo domain. With one exception, the key generator tModel does not allow the user to save keys from subdomains such as uddi:systinet.com:uddiRegistry:demo:businessService:exchangeRate , that is, derived keys of uddi:systinet.com:uddiRegistry:demo:businessService . The key generator tModel, however, permits the user to save the key generator for each direct subdomain. For example, the user can save uddi:systinet.com:uddiRegistry:demo:businessService:keygenerator. After creating this Page 209

5.2.1. Generating Keys