You can implement user authorization using 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 predefined as Web application roles and used for the private UDDI server.
Default UDDI Server Security 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 aadministration 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. |
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com