Why and when to perform this task
Each interface to the UDDI Registry (either through SOAP, EJB or the GUI) is supplied with two roles:The security roles and use of SSL can be altered by users through the Administration Console.
Authentication uses the standard WebSphere facilities and there is no separate registration function for the Registry. If WebSphere security is enabled, you will need to supply your WebSphere userid and password for Publish functions (unless you have changed the supplied Publish role).
If you want to use authentication but do not want to use SSL, you can disable SSL in the standard J2EE manner, by editing the web.xml file for the application, or by using the WebSphere Assembly Toolkit (see Configuring SOAP properties with the ).
You will need to set up the WebSphere security configuration to be used by UDDI. For information on achieving this, refer to Configuring Secure Sockets Layer within this Information Center.
It is expected that, for development use, security will be disabled and that security will be enabled for production environments.
The SOAP interface also supports the UDDI API for get_authToken and discard_authToken API but use of this is optional.
The Security Roles provided with the UDDI Registry are as follows: