Implement user authorization with the use of security roles. Membership in a role determines the level of authorization for a given user. To establish user authorization, map UDDI roles to EAServer roles to implement your own security policy.
The following roles are provided as default Web application security roles in Sybase WorkSpace and are used for the private UDDI server. The default security policy permits unauthenticated users to query the UDDI registry. However, you can modify the policy by specifying which users/groups are authorized for the UddiPublish and the UddiInquire roles.
| Role | Description |
|---|---|
| UddiInquire | Members can search and query the UDDI registry. By default, UDDI does not require the user to be authenticated to search the UDDI server. However, you might not want to do this in a production environment. So, by mapping this role appropriately in a publish or administration capacity, authentication and authorization can be explicitly enforced by the container. |
| UddiPublish | Members can publish information to and query from the UDDI registry. Members of this role can modify or delete only information that they have published. |
| UddiAdmin | Members can modify or delete any information published in the UDDI registry. In addition, members of this role have publish and query privileges, and can add, modify, and delete configuration parameters. Note: In a development environment, you may want to map the UddiAdmin role to the EAServer Admin role, and map the other roles to Everyone. In this case, any authenticated user is considered a member of the role and can publish and query. Only admin@system users can modify published data and UDDI configuration settings.
|
Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com
Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.