User Store PStore Tool - GUI Version

Refresh Properties To synchronize information on the Properties panel with the original user store source, perform a refresh. Select Properties and Refresh Properties from the User Store menu. User Properties Details Panel The Details panel has more information about user properties that depend on the property type. Select the property you want to see. You can also change this value. If you want to store a new value press Apply Changes. To return to the original value, press Restore.

9. SSL Tool

The sslTool helps with setup of SSL on the client side of Oracle Service Registry. The general usage is: sslTool [command [options]] The SSL tool has the following commands: • serverInfo - Prints out security requirements of an SSL server and saves a server certificate to a file. • encrypt - Prints out the encrypted form of a password supplied as plain text. Encrypted passwords are used in the configuration files of Oracle Service Registry. • pstoreEI - Exports and imports a java keystore to or from the Oracle Service Registry Protected Store. Both PKCS12 and JKS keystores are supported. The type of a supplied keystore is automatically detected during import. Running the sslTool with a command followed by a --help option prints out a complete help for the command. See Section 9.1, SSL Tool Examples for the most typical usage.

9.1. SSL Tool Examples

To print out security requirements of an SSL server: sslTool serverInfo --url https:localhost:8443 To print out security requirements of an SSL server and save server certificates: sslTool serverInfo --url https:localhost:8443 --certFile tmpsever.cer To print out an encrypted password for use in Oracle Service Registry configuration files: sslTool encrypt --password changeit To import a key entry from a java keystore to Oracle Service Registry client Protected Store: sslTool pstoreEI -i --keystore tmpjava.keystore --storepass changeit --alias mykey --keypass changeit --pstore ..confclientconf.xml Page 383

9.1. SSL Tool Examples

--pstoreAlias registryclient --pstoreKeypass changeit2 To export a key entry from Oracle Service Registry Protected Store to a java keystore: sslTool pstoreEI -e --keystore tmpjava.keystore2 --storepass changeit --alias mykey --keypass changeit --pstore ..confclientconf.xml --pstoreAlias registryclient --pstoreKeypass changeit2

9.2. Associating an SSL client identity with a registry client

Instructions on how to associate an SSL client identity with a registry client are explained in Section 2.5.1, Example Client . In this case, a key entry must be imported to registrys client protected store, which is the confclientconf.xml file of the registry installation directory and a few system properties must be added to a script that runs the client application. There are also cases where a registry acts as a client to another registry. These include: • Communication between nodes in a clustered Oracle Service Registry. Associating an SSL client identity with an Oracle Service Registry server can be done in the appuddiconfsecurity.xml file of a registry installation directory or deployed package for a deployed registry by adding the destinationConfig elements. A fragment of the security.xml with example destinationConfig elements is shown in Example 1, Association of client identities with a registry server . Example 1. Association of client identities with a registry server ?xml version=1.0 encoding=UTF-8? config name=security savingPeriod=5000 ... security ... security -- For communication with other nodes in the cluster -- destinationConfig aliasclusterClientalias password_codedgNFDFWMNdkU=password_coded destination proxyName=com.systinet.uddi.configurator.cluster.ConfiguratorManagerStub destination proxyName=com.systinet.uddi.configurator.cluster.ConfiguratorListenerStub destinationConfig -- For communication via registry client to services accessible at URLs that start with https:pc1.example.com or https:pc2.example.com -- destinationConfig aliasotherClientalias password_codedVr+i+UzC2WLJXWg0ih6J+Q==password_coded destination url=https:pc1.example.com destination url=https:pc2.example.com destinationConfig config Page 384

9.2. Associating an SSL client identity with a registry client