1. A user attempts to access content via the SAP NetWeaver Enterprise Portal.

   For example, the user may enter the following URL to access an HR application through a proxy server:

   https://host:port/irj

2. The WebGate intercepts the request and queries the Access Server for the security policy that determines if the resource is protected.

   The security policy consists of an authentication scheme, authorization rules, and allowed operations. Based on the authentication and authorization success or failure, specified actions are performed.

   The Access System security policy for the SAP /irj login URL is applicable to all resources accessed using the https://host:port/irj URL.

   Note that the SAP NetWeaver Enterprise Portal has its own authorization system that can be configured to set user access to iViews.

3. If the resource is protected, the WebGate prompts the user for authentication credentials.

   The credentials that the WebGate requests depend on the authentication scheme configured in the Access System, for example, Basic over LDAP or Form-based authentication.

4. If the credentials are validated, the Access System authenticates the user and sets an encrypted ObSSOCookie in the user's browser.

5. After authenticating, the authorization rules defined in the Access System are applied based on the security policy.

   Specific actions are performed based on the authorization rules. If the user is authorized, access to the SAP Portal login (the requested content) is allowed. For SAP Enterprise Portal header variable integration, the Access Server sets the authenticated user ID in a header variable.

   If the user is not authenticated or authorized, he or she is denied access and redirected to another URL, as determined by the administrator. For example, the user may be redirected to an "invalid credentials" page.

6. For the integration with SAP NetWeaver Enterprise Portal, the proxy Web server redirects the request to the SAP NetWeaver Enterprise Portal internal Web server that contains the header variable details.

7. The SAP NetWeaver Enterprise Portal uses the header variable value to check the mapping of the user ID against the configured data source in the portal.

   Both the Access Manager and SAP NetWeaver Enterprise Portal data source must contain the same user ID value.

   Upon successful mapping, SAP NetWeaver Enterprise Portal allows the user to access the requested resource.

   SAP NetWeaver Enterprise Portal sends a response to the proxy, and the proxy redirects to the client browser.

8. All interaction with the SAP Enterprise Portal takes place through the proxy server.

• Install SAP NetWeaver Enterprise Portal before completing the steps in this section.

• Install the Apache HTTP Server by following the installation steps provided by apache.org.

• Install and configure a WebGate on each Apache HTTP Server instance that supports the proxy connection to the SAP Enterprise Portal instance. See Installing Webgates for Oracle Access Manager for details.

• Install Access Manager before completing the steps in Configuring Access Manager for SAP Enterprise Portal. See the Installing and Configuring Oracle Identity and Access Management for details.

• Synchronize the time on all servers where SAP NetWeaver Enterprise Portal and Access Manager components are installed.

• Ensure that the users exist in the Access Manager LDAP directory as well as on the SAP R3 system database.

  The user ID in Access Manager and the SAP database must be the same or be mapped to each other. Any attribute in a user's profile can be configured as the SAP ID and passed directly to SAP. Alternatively, SAP can be configured to map the SAP ID to any user attribute that it receives from Access Manager.

• Verify that the Web browser is configured to allow cookies.

To configure Apache HTTP Server 2.0.x

For more information about configuring authentication schemes for SAP Enterprise Portal, see the SAP documentation.

To configure the header variable

1. Stop the SAP J2EE dispatcher and server.

2. Browse to the following directory:

   SAP_J2EE_engine_install_dir\ume

3. Back up the file authschemes.xml.bak to another directory.

4. Rename authschemes.xml.bak to authschemes.xml.

5. Open authschemes.xml in an editor and change the reference of the default authentication scheme to the authentication scheme header as follows:

   <authscheme-refs>
        <authscheme-ref name="default">
             <authscheme>header</authscheme>
             <authscheme>uidpwdlogon</authscheme>
        </authscheme-ref>
   </authscheme-refs>
   

6. In the authentication scheme header of authschemes.xml, specify the name of the HTTP header variable where the Access System provides the user ID.

   As described in "Configuring Access Manager for SAP Enterprise Portal", this is the OB_USER header variable. You configure this header variable as follows:

   <authscheme name="header">
        <loginmodule>
             <loginModuleName>  
                  com.sap.security.core.logon.imp.HeaderVariableLoginModule 
             </loginModuleName>
                  <controlFlag>REQUISITE</controlFlag>
                  <options>Header=OB_USER</options>
        </loginmodule>
        <priority>5</priority>
        <frontEndType>2</frontEndType>
        <frontEndTarget>com.sap.portal.runtime.logon.header</frontEndTarget>
   </authscheme>
   

   The control flag value REQUISITE means the login module must succeed. If login succeeds, authentication continues through the list of login modules. If it fails, control immediately returns to the application and authentication does not continue through the list of login modules.

7. Restart the portal server and J2EE engine.

   The modified authschemes.xml file will be loaded into the Portal Content Directory (PCD). SAP Enterprise Portal will rename it as authschemes.xml.bak.

To Configure Logout

To adjust the Login Module Stacks for using Header Variables

To configure Access Manager for SAP NetWeaver Enterprise Portal

• Install SAP NetWeaver Enterprise Portal version 7.4.x before completing the steps in this section.

• Install Access Manager as described in the Installing and Configuring Oracle Identity and Access Management.

• Install Apache HTTP Server 2.0.x or 2.2.x by following the installation steps provided by apache.org.

• Install and configure an OAM WebGate on each Apache HTTP Server instance that supports the proxy connection to the SAP Enterprise Portal 7.4 instance. See Installing Webgates for Oracle Access Manager for details.

• Synchronize the time on all servers where SAP NetWeaver Enterprise Portal and Access Manager components are installed.

• Ensure that the users exist in the Access Manager LDAP directory as well as on the SAP R3 system database.

  The user ID in Access Manager and the SAP database must be the same or be mapped to each other. Any attribute in a user's profile can be configured as the SAP ID and passed directly to SAP. Alternatively, SAP can be configured to map the SAP ID to any user attribute that it receives from Access Manager.

• Verify that your Web browser is configured to allow cookies.

To configure:

1. In to the Oracle Access Management Console, click Application Security at the top of the window.

2. In the Launch Pad tab, select Create Application Domain from the Create (+) drop-down menu in the Access Manager section.

3. Complete the form to create a WebGate for this integration. For example:

   Name—Type a meaningful name, for example, SAP_AG. Do not include spaces in the name.

   Version - select OAM from the drop-down menu.

   Access Client Password—Enter a password to be used during the installation of the WebGate.

   Security—Choose the type of communication that should occur between the WebGate and the OAM server.

   Click Apply.

   A confirmation page opens.

4. At the bottom of the confirmation page, in the Server Lists section, associate the WebGate with a defined Access Server.

   Click Apply.

5. On the Launch Pad page, go to the Access Manager section and click Host Identifiers.

   Click Search, then click the WebGate in the search results.

   Configure the host identifiers using the fully qualified proxy machine name and port for the Apache proxy.

6. Click Application Domains and search for the application domain name that you used to create the WebGate (for example, SAP_WG).

   Click the application domain name in the search results to open it

   1. Click the Resources tab and search for the resource that the WebGates should protect. Select the resource in the search results then click the Create button.

      Complete the form and click Apply.

      Type - HTTP

      Resource URL - /irj

      Protection Level - Protected

      Authentication Policy - Protected Resource Policy

      Authorization Policy - Protected Resource Policy

   2. Click the Authentication Policies tab, then click Protected Resource Policy.

      Choose the appropriate authentication scheme from the Authentication Scheme drop-down that you want to configure for this particular domain. For example, for a form-based authentication policy (FAAuthScheme), enter the following:

      Name - Protected Resource Policy

      Authentication Scheme - FAAuthScheme

      Note:

      Select either basic-over-LDAP or form-based authentication.

      Oracle recommends that you use a form-based authentication scheme. If you use the basic authentication scheme, also set the Challenge Redirect field to another WebGate to ensure that the ObSSOCookie is set.

      Click Apply to save your changes.

   3. Click the Authorization Policies tab, then click Protected Resource Policy.

      Click the Responses tab and add the following:

      Type - Header

      Name - OAM_REMOTE_USER

      Value - Same account name

      The other tabs in Authorization Policies include conditions and rules:

      Condition - Creates a list of users and puts them in a group.

      Rule - Allows or denies access to the group of users created in the conditions tab.

      Click Apply to save your changes.

7. If you configured a form-based authentication scheme, ensure that a login.html page is configured in the proxy server document root.

   Also, ensure that a logout.html page is present on the proxy Web server document root. You can create a custom logout page using HTML, a JSP file, or a CGI protocol.

   The default logout page (logout.html) is located here:

   WebGate_install_dir/webgate/apache/oamsso/logout.html

   Where:

   WebGate_install_dir is the directory where the WebGate is installed. Ensure that the name of the logout page contains the string logout.

8. Ensure that the user ID that is returned by the OAM_REMOTE_USER header variable exists in the user management data sources for SAP Enterprise 7.4.

9. On the Launch Pad page, go to the Access Manager section and click Authentication Schemes.

   Choose the authentication scheme to use. This is the scheme that you selected inside the application domain of the WebGate.

To configure:

See the SAP Enterprise Portal 7.4 Enterprise Postal Security Guide for more information about configuring authentication schemes for SAP Enterprise Portal.

In the console, choose Configuration > Authentication and Single Sign-On. Click Login Modules under the Authentication tab. Create the HeaderVariableLoginModule login module, with the display name as HeaderVariableLoginModule and class name as com.sap.security.core.server.jaas.HeaderVariableLoginModule. Choose Component > ticket from the Login Module Use tab, and add the login module HeaderVariableLoginModule to the login module stack for each template or application that is to support header variable authentication.

{ume.configuration.active=true

{ume.configuration.active=true, Header=<header_name>} 

{ume.configuration.active=true} 

	{}

	{ume.configuration.active=true}