Using Liferay SSO with Oracle Access Manager 11g

Well, I was given a challenging task – using Oracle Access Manager 11g as an SSO provider for Liferay 6.0 (the community edition…).
Now, as you might know – there is no built-in OAM support for Liferay – so I was stuck with configuring one myself. Since I didn’t even have the OAM installed – I’ll detail all the steps I did. To simplify matters – I installed OAM on Microsoft Windows Server, but the same should hold for Linux.

All Oracle downloads were downloaded from edelivery.oracle.com. Version is 11.1.0.6.
 

OAM Installation

1. Install Oracle database. I didn’t install Oracle XE, but rather the Enterprise edition.
2. Alter the Oracle database.
   1. Open sqlplus as sys and run the following commands

   alter system set open_cursors=1000 scope=both;
   alter system set processes=1000 scope=SPFILE;
   

3. Restart Oracle DB.
4. Run RCU (V33643-01), and check the Identity Managent checkbox. Proceed with the installation.
5. Install WebLogic Server (wls1036_generic)
6. Install SOA Suite (ofm_soa_generic_11.1.1.6.0_disk1_1of2 and ofm_soa_generic_11.1.1.6.0_disk1_2of2).
7. Install IdM (V33644-01_1of2 and V33644-01_2of2)
8. From your ORACLE_HOME/IDM_HOME/common/bin run the config.cmd file.
9. Install all the required components (especially all the Oracle Access Manager relevant components).
10. DO NOT START THE ADMIN SERVER.
11. Run the following WLST scripts (thank you Warren

$MW_HOME/oracle_common/common/bin/wlst.cmd $ORACLE_HOME/common/tools/configureSecurityStore.py -d $IAM_DOMAIN_LOCATION -m create     -c IAM -p $ORA_PASS
$MW_HOME/oracle_common/common/bin/wlst.cmd $ORACLE_HOME/common/tools/configureSecurityStore.py -d $IAM_DOMAIN_LOCATION -m validate

12. Where
1. $MW_HOME is where you put the Middleware home (e.g. ~/Oracle/Middleware)
   $ORACLE_HOME
2. is the Oracle IAM home (e.g. ~/Oracle/Middleware/Oracle_IAM1)
   $IAM_DOMAIN_
3. LOCATION is the domain home (e.g. ~/Oracle/Middleware/user_projects/domains/OAMDomain)
4. $ORA_PASS is the password needed to talk to the database
13. Now you can safely run the admin server. Connect to it using IP_ADDR:7001/em, and start the OAM managed server too.

Apache installation/configuration

On a separate machine (I used RedHat Linux 5.5):

1. Install Apache2.2
2. Configure WebGate (I used ZIP file oam_int_linux_v10_cd1.zip)
3. Configure Apache to act as a proxy for your Liferay server by using ProxyPass and ProxyPassReverse. For instance:

ProxyRequests Off
ProxyPass /web http://LIFERAY_SERVER:8080/web
ProxyPassReverse /web http://LIFERAY_SERVER:8080/web

4. Configure WebGate in the Apache. On my machine the configuration looked like this:

LoadModule obWebgateModule "/usr/local/webgate/product/access/oblix/apps/webgate/bin/webgate.so"

LoadFile "/usr/local/webgate/libgcc_s.so.1"
LoadFile "/usr/local/webgate/libstdc++.so.6"

        WebGateInstalldir "/usr/local/webgate/product/access"
        WebGateMode PEER
        #webgateload obWebgateModule "/usr/local/webgate/product/access/oblix/apps/webgate/bin/webgate.so"


        SetHandler obwebgateerr


        SetHandler obwebgateerr


        AuthType Oblix
        require valid-user

OAM Configuration

1. Open the Access Manager console, and click on the “New OAM10g WebGate”
2. Fill in the details, exactly as you did during the WebGate installation.
3. Go to “Application Domains”, and select the newly created Application Policy
4. Change any required value, and select “Authorization Policies”
5. Select the “Protected Resource Policy”
6. Select “Responses”
7. Add a new response – HTTP Header with the name of LIFERAY_SCREEN_NAME and value of uid

Liferay Configuration

1. Edit the portal-ext.properties file and add the following line:

auto.login.hooks=com.liferay.portal.security.auth.RequestHeaderAutoLogin

Restart Apache, and browse to it. You should get the OAM login page, and after login – you should see you have automatically logged-in into Liferay…