Web Interface Configuration Figure 54. Registry Console Configuration - Web Interface Tab

Field description: • URL - nonsecure registry URL • Secure URL - secure registry URL • Context - context of the Registry Control URL • Data context - context where static objects such as JavaScript and images are stored • JSP directory - location of JSP pages relative to REGISTRY_HOMEworkuddi • Upload directory - upload directory used for tasks such as uploading taxonomies • Maximum upload size - maximum upload size in bytes • Server session timeout - session timeout measured in seconds • Name cache timeout - cache timeout for the names of UDDI structures. If someone renames a UDDI structure, the Registry Control will load the new name after this interval has passed measured in seconds. • Entity cache enabled - If you check this check box, entities will be cached. Click Save configuration when finished. Page 365 5.1. Web Interface Configuration

5.2. Paging Configuration Figure 55. Registry Console Configuration - Paging Tab

Paging limits - On this tab, you can specify how many records and on how many pages searched data will appear. Click Save configuration when finished.

6. Permissions: Principles

Permissions in Oracle Service Registry were developed so that administrators might exercise control over users. Permissions: • Provide a simple mechanism for the management of users rights in Oracle Service Registry. • Allow the administrator to manage or make available different parts of the registry to different users. • Help Oracle Service Registry better reflect the real world where there are many roles with different responsibilities. This chapter describes permissions in detail with some examples and a description of permission configuration. Page 366

6. Permissions: Principles

Permission is defined as the right to perform an action on some interface. Put another way: permission is the ability to process some method on some interface. Permissions are very different from the other mechanism for rights in Oracle Service Registry, the Access Control List. Access Control enables the user to control access to the basic UDDI data structures businessEntity, businessService, bindingTemplate, and tModel. Access Control on Oracle Service Registry is provided by the Access Control List ACL. The ACL is based on permissions given to a user or group. In the context of ACL, this means that a given user can access only that information in Oracle Service Registry made available to the user by the registry administrator or other users. For more information about the Access Control List, see the Access Control chapter in the Users guide. Access Control Lists limit the visibility of entities and so restrict the access to data in Oracle Service Registry. Permissions on the other hand restrict access to interfaces. The ACLs restrain users by the restricting the visibility of UDDI structures. Permissions limit users through the visibility of interfaces.

6.1. Permissions Definitions

There are two basic kinds of permission: • The first, consisting of ApiUserPermission and ApiManagerPermission , is used to restrict access for some users on some interfaces. • The second, ConfigurationManagerPermission , is used to restrict the ability to change configurations in Oracle Service Registry. ApiUserPermission ApiUserPermission consists of the interfaces name and method from the given interface. This permission provides the user common access to the specified method on the given API. ApiUserPermission enables the user to call methods on an interface as a common user. Users usually must have this permission to perform any call. ApiManagerPermission ApiManagerPermission also consists of the names of an interface and of a method. This permission allows the user to call a determined method on the given API. It is very similar to ApiUserPermission. The only difference is in the users significance. If a user has ApiManagerPermission, that user is considered to be a privileged user. There are many API calls where the result depends on users importance. ConfigurationManagerPermission ConfigurationManagerPermission consists of configuration files and a methods name. The name of the method is either get or set. The ConfigurationManagerPermission combined with the get method allows user to read get data from the configuration file. On the other hand, the ConfigurationManagerPermission combined with the set method enables the user to write to the configuration.

6.2. Oracle Service Registry Permission Rules

The following permissions rules are always valid: • Permission is the ability to process a method on an API. • Permission contains the type of permission ApiUserPermission, ApiManagerPermission, ConfigurationManagerPermission, the name interfaces or configs name and an action methods name. You are allowed to use the asterisk wildcard to substitute all names - names of interfaces, configurations, or actions. • There is no hierarchy in permissions. The ability to set permission for users is also a permission for some methods on PermissionApi. • The Oracle Service Registry administrator has all permissions for all methods on all APIs. Page 367

6.2. Oracle Service Registry Permission Rules