Click Deployments in the Domain Structure navigation tree. On the Control tab, click Next until you see the Oracle UCM deployment you Click Update. Under the Deployment plan path, select Change Path. Verify that Redeploy this application using the followi

5-24 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server client, and the Oracle WebLogic Server domain. Details including system requirements for SSO with Microsoft clients are provided in Configuring Single Sign-On with Microsoft Clients in Oracle Fusion Middleware Securing Oracle WebLogic Server. As part of configuring SSO with Microsoft clients, you must specify an LDAP authentication provider to access the external Microsoft Active Directory. Oracle WebLogic Server offers an LDAP provider already configured for Microsoft Active Directory: the Active Directory Authentication provider. See Configuring LDAP Authentication Providers in Oracle WebLogic Server Securing Oracle WebLogic Server. As part of configuring SSO with Microsoft clients, you must configure the Negotiate Identity Assertion provider in Oracle WebLogic Server security realm. The identity assertion provider decodes Simple and Protected Negotiate SPNEGO tokens to obtain Kerberos tokens, validates the Kerberos tokens, and maps Kerberos tokens to WebLogic users. Use the Oracle WebLogic Server Administration Console to add a new provider in the appropriate security realm in the domain structure, assign it a name, then select NegotiateIdentityAsserter for its Type. Activate the changes and restart the Oracle WebLogic Server. Now your server can use the Kerberos ticket it receives from the browser. You must redeploy each Oracle UCM application Oracle Content Server, Inbound Refinery, Universal Records Management that will be used in the Windows Native Authentication Kerberos environment, using an associated deployment plan. A deployment plan is an XML document. Oracle provides a plan for each of the three Oracle UCM applications: cs-deployment-plan.xml , ibr-deployment-plan.xml , and urm-deployment-plan.xml . You also can implement a deployment plan using the Oracle WebLogic Scripting Tool. 1. Log in to the Oracle WebLogic Server Administration Console.

2. Click Deployments in the Domain Structure navigation tree.

3. On the Control tab, click Next until you see the Oracle UCM deployment you

want to change: ■ Oracle Universal Content Management - Content Server ■ Oracle Universal Content Management - Inbound Refinery ■ Oracle Universal Records Management 4. Select the checkbox to the left of the deployment to be changed.

5. Click Update.

6. Under the Deployment plan path, select Change Path.

Note: When the Oracle WebLogic Server domain for Oracle UCM is configured to use a different authentication provider than the DefaultAuthenticator provider, the new authentication provider must be the first authentication provider listed in the security realm configuration, or Oracle UCM will fail to load any user privileges. Make sure to re-order the authentication providers so the new authentication provider is listed before the DefaultAuthenticator provider. Also ensure that the DefaultAuthenticator control flag is set to SUFFICIENT. For more information, see Section 5.2.3.4, Configuring the First Authentication Provider. Managing Security and User Access 5-25 7. Navigate to and select the appropriate plan file: ■ cs-deployment-plan.xml for Content Server ■ ibr-deployment-plan.xml for Inbound Refinery ■ urm-deployment-plan.xml for Universal Records Management

8. Verify that Redeploy this application using the following deployment files is

selected.

9. Click Next.

10. Click Finish.

11. To verify that SSO with Microsoft clients is configured properly, point a browser to the Microsoft Web application or Web service you want to use. If you are logged on to a Windows domain and have Kerberos credentials acquired from the Active Directory server in the domain, you should be able to access the Web application or Web service without providing a username or password. cs-deployment-plan.xml Use the provided cs-deployment-plan.xml file, or create an .xml file and name it cs-deployment-plan.xml . ?xml version=1.0 encoding=UTF-8? deployment-plan xmlns=http:xmlns.oracle.comweblogicdeployment-plan xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:schemaLocation=http:xmlns.oracle.comweblogicdeployment-plan http:xmlns.oracle.comweblogicdeployment-plan1.0deployment-plan.xsd global-variables=false application-namecs.earapplication-name variable-definition variable namehttp-onlyname valuefalsevalue variable variable-definition module-override module-namecs.warmodule-name module-typewarmodule-type module-descriptor external=false root-elementweblogic-web-approot-element uriWEB-INFweblogic.xmluri variable-assignment namehttp-onlyname xpathweblogic-web-appsession-descriptorcookie-http-onlyxpath variable-assignment module-descriptor module-override deployment-plan ibr-deployment-plan.xml Use the provided ibr-deployment-plan.xml file, or create an .xml file and name it ibr-deployment-plan.xml . ?xml version=1.0 encoding=UTF-8? deployment-plan xmlns=http:xmlns.oracle.comweblogicdeployment-plan xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:schemaLocation= http:xmlns.oracle.comweblogicdeployment-plan http:xmlns.oracle.comweblogicdeployment-plan1.0deployment-plan.xsd global-variables=false 5-26 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server application-nameibr.earapplication-name variable-definition variable namehttp-onlyname valuefalsevalue variable variable-definition module-override module-nameibr.warmodule-name module-typewarmodule-type module-descriptor external=false root-elementweblogic-web-approot-element uriWEB-INFweblogic.xmluri variable-assignment namehttp-onlyname xpathweblogic-web-appsession-descriptorcookie-http-onlyxpath variable-assignment module-descriptor module-override deployment-plan urm-deployment-plan.xml Use the provided urm-deployment-plan.xml file, or create an .xml file and name it urm-deployment-plan.xml . ?xml version=1.0 encoding=UTF-8? deployment-plan xmlns=http:xmlns.oracle.comweblogicdeployment-plan xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:schemaLocation=http:xmlns.oracle.comweblogicdeployment-plan http:xmlns.oracle.comweblogicdeployment-plan1.0deployment-plan.xsd global-variables=false application-nameurm.earapplication-name variable-definition variable namehttp-onlyname valuefalsevalue variable variable-definition module-override module-nameurm.warmodule-name module-typewarmodule-type module-descriptor external=false root-elementweblogic-web-approot-element uriWEB-INFweblogic.xmluri variable-assignment xpathweblogic-web-appsession-descriptorcookie-http-onlyxpath variable-assignment module-descriptor module-override deployment-plan

5.2.4 Configuring Oracle WebLogic Server Web Services

Oracle WebLogic Server Web Services are implemented according to the Web Services for Java EE 1.2 specification, which defines the standard Java EE runtime architecture for implementing Web Services in Java. The specification also describes a standard