Disabling Normal Authentication Authentication Configuration

Note Remember that you cannot log in to WEB user interfaces with the normal login dialog after you disable normal authentication.

8.8. Consoles Configuration

In this section, we will show you how to configure authentication for both Registry Control and Business Service Control. The configuration of consoles is very similar to the configuration of other endpoints. Referring to jar packages The file path REGISTRY_HOMEappuddiweb.jarWASP-INFpackage.xml means the WASP-INFpackage.xml inside the jar package REGISTRY_HOMEappuddiweb.jar. For the Registry Control, modify the file REGISTRY_HOMEappuddiweb.jarWASP-INFpackage.xml with the following: service-endpoint path=web name=WebUIEndpoint1 service-instance=tns:WebUI type=raw other-methods=get accepting-security-providers=HttpBasic service-endpoint path=web name=WebUIEndpoint2 service-instance=tns:WebUI type=raw other-methods=get accepting-security-providers=HttpBasic If you want to set Netegrity SiteMinder provider, use accepting-security-providers=Siteminder For the Business Service Control do the same in the file REGISTRY_HOMEappuddibsc.jarWASP-INFpackage.xml We just set authentication providers for both HTTP and HTTPS protocols. Now, we must specify which protocol consoles will be using for user authentication. The default registry configuration is to use HTTP for browsing and searching. HTTPS is used for publishing. To avoid displaying the login dialog twice, for the first time when accessing via HTTP then the second time when accessing via HTTPS, modify the configuration to use only one protocol. For the Registry Control, modify url and secureUrl elements in the file REGISTRY_HOMEappuddiconfweb.xml to have the same value: urlhttps:servername:8443registryurl secureUrlhttps:servername:8443registrysecureUrl For the Business Service Control, make the same change in the REGISTRY_HOMEappuddibsc.jarconfweb.xml file.

8.9. Outgoing Connections Protected with SSL Client Authentication

Oracle Service Registry can be the client in SSL Client Authentication. This allows the following scenarios: • SOAP Client - This is commonly used in following scenarios • Approval process • Replications Page 140

8.9. Outgoing Connections Protected with SSL Client Authentication

• Cluster Approval processes, Replications, and Cluster functionality connect via SOAP endpoints. Deployment in these scenarios does not usually require SSL protection because all registries are located in a dedicated internal network, but Oracle Service Registry can be configured to use client SSL certificates in these scenarios. When the registry on the other side is protected with Client SSL Authentication and plain HTTP connection is not allowed, your registry must connect with an SSL Certificate. This can be achieved by configuring destinationConfig inside security.xml. See the documentation for sslTool in the Administration Guide, which describes the tool for SSL related tasks and destinationConfig . Destination config allows you to specify different certificates for different endpoints by either specifying the SOAP stub or the URL prefix. • HTTPS protected resources • WSDL • XML • XSD • XSLT Resources which are downloaded for processing by Oracle Service Registry can be behind HTTPS protected by Client SSL Authentication. Oracle Service Registry can be set up so that these connections use a specified certificate. The certificate must be present as a key entry inside pstore.xml. This key entry is identified by its alias. The alias and password has to be specified in REGISTRY_HOMEappuddiconfsecurity.xml inside security which is contained in config as shown in example: sslConnectionAliasmyAliasNamesslConnectionAlias sslConnectionPassword_coded9vTJ9GKyjIURFY0qrWvADA==sslConnectionPassword_coded To get encoded password from clear-text password, use REGISTRY_HOMEbinsslTool.bat or .sh with encrypt option.

9. Migration

Migration is used to migrate data from one database to another. You can migrate data during installation or during setup.

9.1. Migration using Setup Tool

To migrate data after installation, use the Setup tool described in Section 2.7, Reconfiguring After Installation . Briefly: 1. Launch the Setup tool by issuing the following command from the bin subdirectory of your installation: setup.bat Windows: .setup.sh UNIX: See command-line parameters in Section 2.6.1, Setup . 2. Select the Migration tool on the first panel: Page 141

9.1. Migration using Setup Tool