Appendix: Disabling Authentication on Oracle WebLogic Server

The Feed Publishing Framework requires that the Oracle WebLogic Server's own authentication be disabled. Disabling Oracle WebLogic Server's authentication allows authentication to be passed through and handled by the PeopleSoft servlet. The config.xml file is shipped with this authentication disabled and, therefore, no action is required unless you have changed the setting in this file.

Note. IBM WebSphere does not require any special configuration steps.

Configuring Oracle WebLogic Server to Disable Authentication

By default, the delivered config.xml file is set to disable the Oracle WebLogic Server's own authentication. No additional configuration is required unless you have changed this authentication setting.

To configure Oracle WebLogic Server to disable authentication:

1. Stop the web server.

2. Go to the PS_HOME\webserv\web_server\config folder.

3. Edit the config.xml file by adding the following tag before the closing </security-configuration> tag:

   <enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>

   The edited file looks similar to the following with the added line in bold near the end:

   
     <security-configuration xmlns:xacml="http://www.bea.com/ns/weblogic/90/security⇒
   /xacml">
       <name>peoplesoft1</name>
       <realm>
         <sec:authentication-provider xsi:type="wls:default-authenticatorType"/>
         <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
           <sec:active-type>AuthenticatedUser</sec:active-type>
         </sec:authentication-provider>
         <sec:role-mapper xsi:type="xacml:xacml-role-mapperType"/>
         <sec:authorizer xsi:type="xacml:xacml-authorizerType"/>
         <sec:adjudicator xsi:type="wls:default-adjudicatorType"/>
         <sec:credential-mapper xsi:type="wls:default-credential-mapperType"/>
         <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"/>
         <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
         <sec:name>myrealm</sec:name>
       </realm>
       <default-realm>myrealm</default-realm>
       <credential-encrypted>{3DES}XLLC9Wru5qKeMAlvEULruO9LodVs7o3du4WVMtMs/⇒
   ffmyP16aD4NKEv0va5IxytcWvGRV50mB5dYbzhos9XWNN0Lz4mQoXiy</credential-encrypted>
       <node-manager-username>system</node-manager-username>
       <node-manager-password-encrypted>{3DES}c/WblCLbZubUdNamvjN1sw==</node-⇒
   manager-password-encrypted>
     ​  <enforce-valid-basic-auth-credentials>false</enforce-valid-basic-⇒
   auth-credentials>
   ​</security-configuration>

4. Save the file.

5. Restart the web server.