Go to primary content
Agile Product Lifecycle Management Administrator Guide
Release 9.3.3
E39286-04
  Go To Table Of Contents
Contents
Previous
Previous 		  

A Configuring Single Sign-On

Agile PLM has the possibility of integrating aspects of your PLM system with Single Sign-On (SSO) capability.

A.1 Overview of Single Sign-On in PLM

With SSO configured and enabled for your PLM system, a user that has signed in to the system once (for instance, through the corporate portal) is not prompted again by a "login" dialog in such cases as:

  • Launching Web Client

  • Clicking on a URL for an email notification

  • When a customer's supplier launches the Microsoft Excel-based Solution from a Declaration

  • When Web Client times out.


Note:

SSO is a Web-based solution that can be enabled only for Agile Web Client. SSO cannot be configured or applied from Java Client, Administrator module in Java Client, or the Agile SDK.

Single Sign-on integrates with the centralized security management, other business and training applications, and improves user productivity in Agile Web Client environment.

The sections below give a general overview to Single Sign-On in Agile PLM, followed by steps to configure and deploy SSO with Windows NTLM.

Figure A-1 Overview of Single Sign-On in PLM

Overview of Single Sign-On in PLM

A.2 Configuring and Deploying SSO with Windows NTLM

The following sections outline the steps to configure and deploy NTLM for Single sign-on capability.

A.2.1 SSO NTLM Authentication

Figure A-2 SSO NTLM Authentication

SSO NTLM Authentication

A.2.2 Configure SSO for Windows NTLM

Microsoft Windows NTLM has been certified for Agile PLM. Discuss your company's needs with your Oracle Consulting - Agile Practice representative.

A.2.2.1 Configure IIS Proxy with WLS

These are the steps to configure Windows NTLM for Single sign-on with Internet Information Services (IIS) as proxy server for WLS.


Note:

The prerequisite for this configuration is that the Windows server on which IIS is running has been joined to a Windows domain. "Microsoft Active Directory" is the name of the Windows Domain controller since Windows 2000.

Install and enable Windows Authentication in IIS for site to use Windows NT LAN Manager for authentication:

  1. Navigate to Administrative Tools > Service Manager.

  2. Navigate to Roles > Web Server

  3. Right-click Add Role and Install Windows Authentication.

  4. Navigate to IIS.

  5. Click Default Site.

  6. Double-click Authentication.

  7. Enable Windows Authentication.

  8. Disable Anonymous Authentication.

  9. In Site Authentication page, select Windows authentication.

  10. Click Providers.

  11. Make NTLM Provider as First.


Note:

Agile 933 PLM with WLS12C must be installed and IIS7.5 Proxy configuration must be completed before proceeding to further steps.

IIS7.5 Proxy Configuration with Agile PLM:

  1. Install and configure the WebLogic plug-in patch.

    1. Download the WLSPlugin11g-IIS6-IIS7-IIS75-win64-x64.zip from the location

      http://www.oracle.com/technetwork/middleware/ias/downloads/wls-plugins-096117.htm

    2. Extract the plug-in zip to location

      C:\myhome\weblogic-plugins-1.1

    3. Create iisproxy.ini file in %PLUGIN_HOME%\lib\ with the settings below:

      WebLogicHost=wls-host

      WebLogicPort=wls-port

      Debug=ALL

      WLLogFile=C:\Temp\wl-proxy.log

    4. Ensure that the %PLUGIN_HOME%\lib is included in the system PATH:

      Control-Panel > System > System Properties > Environment Variables > System Properties > PATH

    5. Open IIS Manager; use Default Web Site or create a Web Site.

    6. Click the site.

    7. Open Handler Mappings and add a script map:

      Set the Extension to like '*'

      Set Executable to %PLUGIN_HOME%\lib\iisproxy.dll, and give a Name.

    8. Start IIS.

A.2.2.2 Configure PLM for NTLM with WLS

A. To configure your PLM system for SSO with NTLM, perform these operations.


Important:

Stop the Agile Server. For information on how to stop the Agile PLM server, see the Installing Agile PLM on Oracle WebLogic Server guide.

  1. In the WLS console, go to Summary of Security Realms > AgileRealm > Providers.

  2. Click New and add "AgileIdentityAsserter" as the AgileRealm Authentication Provider.

  3. Open the added AgileIdentityAsserter, select the Active type as Authorization (the AGILESSO is already a default value there). Both should be selected.

  4. Click Save, then click Activate the Changes, and then logout from the console.

  5. Stop the Application server.

B. Edit this file:

agile_home/agileDomain/applications/application.ear/application.war/WEB-INF/web.xml.

WLS 12C supports multiple authentication methods. Add the following elements:

<login-config>

<auth-method>client-cert, form</auth-method>

<realm-name>AgileRealm</realm-name>

<form-login-config>

<form-login-page>/default/login-cms.jsp</form-login-page>

<form-error-page>/default/loginError.jsp</form-error-page>

</form-login-config>

</login-config>

C: Perform the following setting modifications for the action "CLICK ON LOGIN UPON LOGOUT SHOULD LOGIN AUTOMATICALLY IN SSO ENABLE SYSTEM".

Edit this file:

agile_home/agileDomain/config/agile.properties

  • Set the agile.sso.enabled value in agile.properties to the following:

    agile.sso.enabled= true

  • Set the agile.sso.cookie.name in agile.properties to the following:

    agile.sso.cookie.name=AGILESSO


Note:

Manually add agile.sso.enabled property in the agile.properties file located in agile_home/agileDomain/config and set the value to true.

D. Restart the Agile server.

E. Ensure that NT user name and password exist in DB:

Ensure that the NT user name and password exist in the DB to which the application is connected (by migrating from Microsoft Active Directory Domain LDAP Server. Refer to "LDAP" for information about configuring the LDAP server, migrating users and activation) to which the application is connected.

F. Set Web Server Proxy URL in Agile PLM Administrator:

  1. Log in to Java Client as administrator.

  2. Navigate to the Location node.

  3. Enter the Web Server Proxy URL.

  4. Restart the File Manager.

G. Attempt to access the Proxy URL in your Windows computer:

  • In IE browser, it should automatically login to Agile PL M.

  • In Firefox browser, it will ask for your network credentials only for the first time access.

A.2.3 RMW SSO Configuration

If the Recipe & Material Workspace application is configured with the Agile 9.3.x SSO environment, the system administrator needs to update the Agile Proxy (SSO) URL in the CFMConfig.xml of "<AgileHome>\AgilePharma\config".

The entry must be changed to read:

<AgileSSOProxyUrl> </AgileSSOProxyUrl>

For more information about the system configuration of Agile Recipe & Material Workspace, see the Recipe & Material Workspace Administrator Guide.

A.3 Deploy NTLM

The following are possible SSO deployment scenarios with NTLM, one for secure proxy and one for transparent or no proxy.

A.3.1 With Secure Proxy

With this deployment, authentication takes place on the proxy server, so it is recommended for those companies that use a proxy server.

Request flow with this deployment:

  1. User launches browser to access Agile PLM (for example, http://agileplm.xyz.com/Agile/PLMServlet).

  2. The NTLM-enabled IIS server challenges the browser for credentials.

  3. After a successful NTLM handshake, the request reaches Agile Application Server (AAS) agent with user information.

NTLM is a connection-based authentication protocol. For each new socket connection between client and server (or proxy), it has to exchange credentials by sending and responding to HTTP requests and responses.

  1. The AAS agent passes the user information to the application server security framework.

  2. The user will be allowed to access Agile applications.

This authentication happens whenever the client sends an HTTP POST request; therefore, authentication can re-occur even during an established user session.

A.3.2 With Transparent Proxy or No Proxy

Request flow with this deployment:

  1. User launches browser to access Agile (for example, http://agileplm.xyz.com/Agile/PLMServlet).

  2. The Agile Application Server (AAS) agent installed on server challenges the browser for credentials.

  3. After a successful NTLM handshake, the AAS agent passes the user information to the application server security framework.

  4. The user will be allowed to access Agile applications.

A.4 The Oracle Access Manager

Oracle Access Manager (OAM) ensures authentication and strict authorization policies are applied to your applications and services such as:

  • Controlled access to web applications, Enterprise Java Beans (EJB) applications, J2EE resources, and common packaged enterprise applications.

  • Web SSO for secure access to multiple applications with one authentication step.

  • Flexible authentication support.

Agile PLM 9.3.3 is certified with OAM (12g) suite of products.

A.5 OAM 11g Configuration with Agile PLM 9.3.2

This section covers Oracle Access Manager (OAM) 11g configuration with Agile PLM.

A.5.1 OAM11g Configuration with Agile PLM 9.3.3 Using IIS 7.5 Web Server

Perform the prerequisite steps, and then perform the configuration steps as explained in the following sections.

A.5.1.1 IIS 7.5 Web Server Configuration Prerequisites

Ensure the following components have been downloaded and installed.

  1. Installed/configured and tested IIS 7.5 webserver with Agile 9.3.2 (Agile should be installed on WLS12C). You can refer to the Knowledge Base for details.

  2. Download OAM WebGate 10g for IIS from the site:

    http://www.oracle.com/technetwork/middleware/ias/downloads/101401-099957.html

    1. Get oam_int_win_v11_cd1.zip from disk2 for windows.

    2. Extract and start installation using Oracle_Access_Manager10_1_4_2_5_Win64_ISAPI_WebGate.exe

  3. Now install OAM WebGate 10g on the same system where IIS 7.5 webserver has been installed.

    Ensure that IIS7.5 is installed with all Role Services. If not, you can add those from Server Manger. Navigate to Web Server, right click, Add Role Services. Add all role services. You can refer to the Knowledge Base for details.

The following sections/main steps explain the configuration of the OAM11gR2 Server with the Agile PLM 933 application:

A.5.1.2 OAM WebGate Registration in OAMServer (IIS 7.5)

To perform OAM WebGate Agent registration in OAMServer:

  1. Create a WebGate entry on OAM console through UI mode Steps:

    1. Click New OAM WebGate 10g in welcome page.

    2. Enter the Name. The host identifier will populate automatically.

    3. Click Apply.

      Figure A-3 OAM WebGate Agent Registration

      OAM WebGate Agent registration

A.5.1.3 IIS 7.5 Webserver Configuration with WebGate

The following steps must be performed after the installation of OAM10g WebGate for IIS 7.5 Webserver:

  1. Navigate to Site-ISAP Filters tab and add Filter OracleWebGate point to webgate.dll.

  2. Navigate to Site.

    1. Right-click Add Application.

    2. Give alias name as access and point physical path to Web Gate\access folder.

  3. Navigate to Host Level.

    1. Click ISAPI and CGI Restrictions.

    2. Click Add.

    3. Add the path to webgate.dll and type description as OracleWebGate.

    4. Select check box Allow extension path to execute.

    5. Click OK.

  4. Navigate to Web Gate/access.

    1. Right click Properties.

    2. Navigate to Security.

    3. Assign Full Control to Everyone.

  5. Restart IIS.

A.5.1.4 WebLogic Proxy Configuration for IIS 7.5 Webserver

To configure WebLogic proxy for IIS 7.5 Webserver:

  1. Ensure that you have installed and configure the WebLogic proxy plug-in patch for IIS 7.5 Webserver.

    You can download the WLSPlugin11g-IIS6-IIS7-IIS75-win64-x64.zip from the location:

    http://www.oracle.com/technetwork/middleware/ias/downloads/wls-plugins-096117.html

  2. Extract the plug-in zip to location C:\myhome\weblogic-plugins-1.1.


    Note:

    This will be referred as the variable PLUGIN_HOME going forward.

  3. Create iisproxy.ini file in %PLUGIN_HOME%\lib\ with below details:

    WebLogicHost=wls-host

    WebLogicPort=wls-port

    Debug=ALL

    WLLogFile=C:\Temp\wl-proxy.log

    WLExcludePathOrMimeType=/obrar.cgi

  4. Ensure that the %PLUGIN_HOME%\lib is included in the system PATH

    (Control-Panel > System > System Properties > Environment Variables > System Properties > PATH)

  5. Open IIS Manager, use 'Default Web Site' or create a 'Web Site' based on your needs.

    1. Click the site.

    2. Open 'Handler Mappings' and add a script map

    • Set the 'Extension' like '/Agile/*'

    • Set 'Executable' to %PLUGIN_HOME%\lib\iisproxy.dll

    • Give a 'Name'

  6. Create new directory oamsso under

    <IIS inetpub>\wwwroot\

    and copy file logout.html to oamsso folder from OAM server

    <Middleware Home>\user projects\domains\oam_domain\output\<933IIS Agent>

  7. Navigate to Host Level and click on ISAPI and CGI Restrictions and click on Add, add the path to iisproxy.dll and select allow extension path to execute.

  8. Open IIS Manager, use either 'Default Web Site' or create a 'Web Site'.

    1. Click on the site.

    2. Double-click on Request Filtering in right pane.

    3. Click Edit Feature Settings in Actions pane.

    4. In Edit Request Filtering Settings Dialog, change Maximum query string (Bytes) to:

      4096

    5. Click OK.


      Note:

      If you need to add any protect and unprotect resources to work with specific functionality, then add those resource URLs as handler mappings by following the same process above.

  9. Restart IIS.

A.5.1.5 OAM Webgate Configuration for IIS 7.5 Webserver

To configure OAM WebGate:

  1. Add the authorization policy as below:

    1. Navigate to OAM Console > Policy Configuration > Applications domain > Agent (Name of the Agent in this case) > Authorization Policies.

    2. Open Protected Resources Policy.

    3. Navigate to Response tab.

    4. Add Response as below:

      Name= remote-user

      Type=Header

      Value=$user.attr.dn

    5. Click Apply.

  2. Configure Resources for Web gate:

    1. Add these resources with webroot context (in this case Agile):

      Add resource URLs

      /Agile

      /Agile/…/*

      with Authentication and Authorization policy as Protected Resource Policy.

      Figure A-4 Add resource URLs

      Add resource URLs IIS Webserver

    2. Exclude the Resources for Gantt Chart.

      You must exclude the below static resources to work on Gantt chart with WebGate. Also use the webroot context while creating Resources to exclude.

      Navigate to OAM Console > Policy Configuration > Applications domain > Open WebGate10g Agents.

      Click Resources.

      In the Resources window, click Search.

      Add the following Resource Types by using the Create button. IN the Create New page:

      Select Type as HTTP.

      Select the Host Identifier of the Web Gate Agent.

      Type the Resource URL with webroot context.

      Select Protection level as Excluded.

      Add the resources as shown in the following figure.

      Figure A-5 Add resources for Gantt chart

      Add excluded resources for Gantt chart, IIS Webserver

A.5.1.6 Agile PLM Configuration for IIS 7.5 Webserver

  1. Navigate to the WebLogic console where the Agile application is installed and create AgileIdentityAsserter.

    1. In WLS Console:

      Click Lock and Edit.

      Move to Summary of Security Realms >AgileRealm >Providers.

      Click New.

      Create AgileIdentityAsserter Authentication with "AgileIdentityAssertion" Provider.

    2. Open the added AgileIdentityAsserter.

    3. Select the Active type as remote-user and Save.

    4. Click Activate Changes.

    5. Logout from the console.

  2. Open agile.Properties file, and add the below settings:

    oam.header.name=remote-user

    oam.sso.logout.url=/oamsso/logout.html?end_url=/Agile/PLMServlet


    Note:

    Where /Agile is the web-root context for the installed application.

  3. Open the Web.xml (\application.ear\application.war\WEB-INF\ web.xml) and change auth-method as below:

    <auth-method>client-cert, form</auth-method>

  4. Restart the WebLogic Application Server where the Agile Application is installed.

  5. Configure LDAP Server (which is used as identity store in OAM) with Agile, Migrate LDAP Users into Agile Application and Activate LDAP users.

  6. Login to Agile Java Client.

    Navigate to the Location node.

    Enter the Web Server Proxy URL.

    Restart the File Manager.

A.5.1.7 Testing (IIS 7.5)

  1. Attempt to login to Agile Proxy URL with the IIS 7.5 webserver port number as configured.

    You should see the OAM Credentials page.

  2. Enter the appropriate OAM (Configured LDAP Identity store user) username and password and the Agile application home page should be presented.

A.5.2 OAM11gR2 Configuration with Agile PLM 9.3.3 Using OHS11gR2 Web Server

Perform the prerequisite steps, and then perform the configuration steps as explained in the following sections.

A.5.2.1 OHS11gR2 Web Server Configuration Prerequisites

Ensure the following components have been downloaded and installed.

  1. Installed WebTier Patch set6(11.1.1.7.0)-forOHS11g on top of Web Logic 10.3.6.

    This should be installed with "Install and Do Not Configure" option. Refer to the Knowledge Base for more details.

  2. Configure only Oracle HTTP Server (OHS) without selecting the component 'Web Cache' and without selecting 'Associate Selected components with Web Logic domain' option.

  3. Installed Web gate 11g R2 (11.1.2.1.0) for OHS11g

The following sections/main steps explain the configuration of the OAM11gR2 Server with the Agile 933 Application:

A.5.2.2 OAM WebGate Registration in OAMServer (OHS11g Webserver)

Create WebGate11g Agent in OAM Console:

Figure A-6 Create WebGate11g Agent

Create WebGate11g Agent

A.5.2.3 OAM WebGate Configuration for OHS11g Webserver

A. The following steps are required to be performed post installation of WebGate11g for OHS11g Webserver on the Server where you installed your OHS and WebGate.

  1. Deploy WebGate:

    • Go to the directory <Middleware Home>\<Web Gate Home>\webgate\ohs\tools\deployWebGate>

    • Run the batch file as below:

      deployWebGateInstance.bat -w <Middleware Home>\<WebTierHome>\instances\instance1\config\OHS\ohs1 -oh C<Middleware Home>\<Web Gate Home>

    You should see the following sample on the console:

    Copying files

    C:\WLS1036\Oracle_OAMWebGate1\webgate\ohs\config\oblog_config_wg.xml

    1 File(s) copied

    C:\WLS1036\Oracle_OAMWebGate1\webgate\ohs\tools\openssl\simpleCA\cacert.pem

    1 File(s) copied

    C:\WLS1036\Oracle_OAMWebGate1\webgate\ohs\tools\openssl\simpleCA\cakey.pem

    1 File(s) copied

  2. Add to the PATH in Environment Variables:

    <Middleware Home>\<Web Gate Home>\webgate\ohs\lib; <Middleware Home>\<WebTier Home>\bin;

  3. Update httpd.conf with the WebGate configuration:

    <Middleware Home>\<Web Gate Home>\webgate\ohs\tools\EditHttpConf>EditHttpConf.exe -w

    <Middleware Home>\<WebTier Home>\instances\instance1\config\OHS\ohs1 -oh <Middleware Home>\<Web Gate Home>\

    You should see the following sample on the console:

    The web server configuration file was successfully updated

    C:\WLS1036\Oracle_WT1\instances\instance1\config\OHS\ohs1/httpd.conf has been backed up as C:\WLS1036\Oracle_WT1\instances\instance1\config\OHS\ohs1/httpd.conf.ORIG

  4. Copy the cwallet.sso and ObClientAccess.xml file from OAM Server:

    From location <Middleware Home >\user_projects\domains\oam_domain\output\OHS11G in OAM Server

    To Web Tier instance directory: <Middleware Home>\<WebTier Home>\instances\instance1\config\OHS\ohs1\webgate\config

B. Add the authorization policy:

  1. Navigate to OAM Console > Policy Configuration > Applications domain > Agent (Name of the WebGate11g Agent in this case) > Authorization Policies.

  2. Open Protected Resources Policy.

  3. Navigate to Response Tab.

  4. Add Response as below:

    Name= remote-user

    Type=Header

    Value=$user.attr.dn

  5. Click Apply.

C. Add user defined parameters for OHS11g WebGate Agent in OAM Console:

  1. Navigate to OAM Console > System Configuration > Access Manager Settings >S SO Agents > OAM Agents > WebGate 11G Agent.

  2. Add the below parameters to User Defined Parameters attribute:

    UniqueCookieNames=enabled

    filterOAMAuthnCookie=false

  3. Click Apply.

D. Configure resources for WebGate::

  1. Add these resources with webroot context (in this case Agile):

    Add resource URLs

    /Agile

    /Agile/…/*

    with Authentication and Authorization policy as Protected Resource Policy.

    Figure A-7 Add resources

    Add resources Linux

  2. Exclude the Resources for Gantt chart:

    We Need to Exclude the below static resources to work on Gantt chart with WebGate. Also use the webroot context while create Resources to exclude.

    1. Navigate to OAM Console > Policy Configuration > Applications domain > Open WebGate Agents.

    2. Click Resources.

    3. In the Resources window, click Search.

    4. Add the following Resource Types using Create Button.

      In Create New page:

      Select Type as HTTP.

      Select the Host Identifier of the Web Gate Agent.

      Type the Resource URL.

      Select Protection level, Authentication Policy.

      Add the resources as shown in the following figure:

      Figure A-8 Add resources

      Add resources OHS11G

A.5.2.4 WebLogic Proxy Plug-in Configuration for OHS 11g Web Server

  1. Navigate to <Middleware Home>\<WebTier Home>\instances\instance1\config\OHS\ohs1

  2. Edit the file mod_wl_ohs.conf file and add below information:

    <IfModule weblogic_module>
           WebLogicHost <wls host>
           WebLogicPort <wls port>
           Debug ON
           WLLogFile C:\Temp\weblogicOHS.log
     </IfModule>
    <Location /Agile>
         SetHandler weblogic-handler
    </Location>
   <Location /JavaClient>
       SetHandler weblogic-handler
  </Location>

    Where /Agile is the web root context of the Agile application.

  3. Navigate to <Middleware Home>\<WebTier Home>\ohs\conf and edit the file httpd.conf and add the following lines:

    # Include the configuration files needed for mod_weblogic
include "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/mod_wl_ohs.conf"
# Include the SSL definitions and Virtual Host container
include "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/ssl.conf"
# Include the admin virtual host (Proxy Virtual Host) related configuration
include "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/admin.conf"
include "moduleconf/*.conf"
include "<Middleware Home>\<WebTier  Home>\instances\instance1\config\OHS\ohs1/webgate.conf"

A.5.2.5 Agile PLM Configuration for OHS11g

  1. Navigate to the WebLogic console where the Agile application is installed and create AgileIdentityAsserter.

    1. In WLS Console:

      Click Lock and Edit.

      Move to Summary of Security Realms >AgileRealm >Providers.

      Click New.

      Create AgileIdentityAsserter Authentication with "AgileIdentityAssertion" Provider.

    2. Open the added AgileIdentityAsserter.

    3. Select the Active type as remote-user and Save.

    4. Click Activate Changes.

    5. Logout from the console.

  2. Open agile.Properties file, and add the below settings:

    oam.header.name=remote-user

    oam.sso.logout.url=/oamsso/logout.html?end_url=/Agile/PLMServlet


    Note:

    Where /Agile is the web-root context for the installed application.

  3. Open the Web.xml (\application.ear\application.war\WEB-INF\ web.xml) and change auth-method as below:

    <auth-method>client-cert, form</auth-method>

  4. Restart the WebLogic Application Server where the Agile Application is installed.

  5. Configure LDAP Server (which is used as identity store in OAM) with Agile, Migrate LDAP Users into Agile Application and Activate LDAP users. See "Agile LDAP Configuration" to configure LDAP Server with Agile PLM.

  6. Login to Agile Java Client.

    Navigate to the Location node.

    Enter the Web Server Proxy URL.

    Restart the File Manager.

A.5.2.6 Testing (OHS 11g)

  1. Attempt to login to Agile Proxy URL with the IIS 7.5 webserver port number as configured.

    You should see the OAM Credentials page.

  2. Enter the appropriate OAM (Configured LDAP Identity store user) username and password and the Agile application home page should be presented.

A.5.3 OAM11gR2 Configuration with Agile PLM 9.3.3 Using Apache 2.2 Web Server

Perform the prerequisite steps, and then perform the configuration steps as explained in the following sections.

A.5.3.1 OAM 11gR2 Configuration Prerequisites (Apache 2.2)

Ensure the following components have been downloaded and installed.

  1. Download Apache2.2 from Apache site and install/configure and test Apache2.2 with Agile 9.3.3 (Agile should be installed on WLS12C). You can refer to the Oracle Knowledge Base for details.

  2. Download and install OAM WebGate 10g for Apache 2.2 from

    http://www.oracle.com/technetwork/middleware/ias/downloads/101401-099957.html

    and install it on the same system where Apache web server has been installed.

    You can refer to the Oracle Knowledge Base document 1526342.1 for details: https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=1526342.1

The following sections/main steps explain the configuration of the OAM11g Server with the Agile 932 Application:

A.5.3.2 WebGate Agent Configuration in OAM Server (Apache 2.2)

You must add a WebGate Agent for the Apache Webserver in the OAM Server using RREG tool.

To perform OAM WebGate Agent registration in OAMServer:

  1. Create a WebGate entry on OAM console through UI mode Steps:

    1. Click on New OAM WebGate 10g in welcome page.

    2. Enter the Name. The host identifier will populate automatically.

    3. Click Apply.

Figure A-9 Adding a WebGate Agent

Surrounding text describes Figure A-9 .

A.5.3.3 OAM WebGate Configuration (Apache 2.2)

OAM WebGate Configuration

  1. Edit httpd.conf under Apache2.2\conf folder and perform the following actions to Configuring Centralized Logout:

    Add the below lines in httpd.conf file:

    #*******Default Login page alias***

    Alias /oamsso "/scratch/qa/webgate/access/oamsso"

    <LocationMatch "/oamsso/*">

    Satisfy any

    </LocationMatch>

    #**********************************

  2. Copy file logout.html to oamsso folder from OAM server <Middleware Home>\user projects\domains\oam_domain\output\<Apache933 Agent>

  3. Restart Apache.

  4. Configure Resources for WebGate:

    1. Add these resources with webroot context (in this case Agile):

      Add resource URL's ” /Agile, /Agile/…/* ” with Authentication and Authorization policy as Protected Resource Policy

      Figure A-10 Add WebGate Resources

      Surrounding text describes Figure A-10 .

    2. Exclude the Resources for Gantt chart:

      We need to exclude the below static resources to work on Gantt chart with WebGate. Also use the webroot context while create Resources to exclude.

      1. Navigate to OAM Console > Policy Configuration > Applications domain > Open WebGate Agents

      2. Click Resources.

      3. In the Resources window, click Search.

      4. Add the following Resource Types using Create Button. In Create New page:

        Select Type as HTTP.

        Select the Host Identifier of the WebGate Agent.

        Type the Resource URL with webroot context

        Select Protection level as Excluded

        Add the resources as below:

        Figure A-11 Add Resource Types

        Surrounding text describes Figure A-11 .

A.5.3.4 Agile PLM Application Configuration (Apache 2.2)

  1. Navigate to the WebLogic Administration console where the Agile application is installed and create AgileIdentityAsserter.

    1. In WLS Console, click Lock and Edit.

    2. Move to Summary of Security Realms >AgileRealm >Providers.

    3. Click New and Create AgileIdentityAsserter Authentication with "AgileIdentityAssertion" Provider.

    4. Open the added AgileIdentityAsserter.

    5. Select the Active type as remote-user and then Save.

    6. Click Activate Changes and logout from the console.

  2. Open agile.Properties file, add the below settings:

    oam.sso.logout.url=/oamsso/logout.html?end_url=/Agile/PLMServlet


    Note:

    Where /Agile/PLMServlet is the web-root context for the installed application.

  3. Open the Web.xml (\application.ear\application.war\WEB-INF\ web.xml) and change auth-method as below:

    <auth-method>client-cert, form</auth-method>

  4. Restart the WebLogic Application Server where the Agile Application is installed.

  5. Configure LDAP Server (which is used as identity store in OAM) with Agile.

  6. Migrate LDAP Users into Agile Application and Activate LDAP users. For more information, see "Agile LDAP Configuration" to configure LDAP Server with Agile.

  7. Login to Agile Java Client.

    Navigate to Location node.

    Enter Web Server Proxy URL.

    Restart the File Manager.

A.5.3.5 Testing (Apache 2.2)

  1. Attempt to login to Agile Proxy URL with the Apache webserver port number as configured.

    You should see the OAM Credentials page.

  2. Enter the appropriate OAM (configured LDAP Identity store user) username and password and the Agile application home page should be presented

  Previous
Previous 
  Go To Table Of Contents
Contents