Working with Access Server SDK 10.1.4.3 and OAM 10g

Hi All,

I’ve written a post earlier about working with 10g Access Gates using Oracle Access Manager 11g. Today, I would like to give insights into implementation of 10g Access Gates using Oracle Access Manager 10g. Access Server SDK 10g is used for Access Gates where out of the box webgates are not available for a web server.

In OAM 10g, Access Server SDK is available in both 32-bit and 64-bit modes in Windows/Linux environments.

1. First and foremost, download the right Access Server SDK installer for your environment. Go through this ReadMe document to know more about existing Access Server SDK versions.
2. Create Host identifier in OAM Access Console.
3. Create Access Gate instance in OAM Access Console. You will need to specify the details AccessGate Name, Hostname, Access Gate Password, Transport Security, Access Management Service, Primary HTTP Cookie Domain, Preferred HTTP Host. You can also specify other Access Gate parameters such as Debug mode, Session timeouts etc.,
4. Create Policy domain in OAM Policy Manager for the custom application. Specify the authentication scheme, authorization rules etc., accordingly.
5. Goto the machine where Access SDK needs to be installed. Install the Access Server SDK with proper user privileges.
6. Goto the directory %ACCESS_SDK_INSTALL_DIR%/oblix/tools/configureAccessGate where %ACCESS_SDK_INSTALL_DIR% is the Access Server SDK installed directory.
7. Configure the Access Gate using the below command configureAccessGate.exe -i %ACCESS_SDK_INSTALL_DIR% -t AccessGate -w <<ACCESS_GATE_NAME>> -m <<SECURITY_MODE as open/simple/cert>> -P <<ACCESS_GATE_PASSWORD>> -h <<ACCESS_GATE_HOSTNAME>> -p <<ACCESS_GATE_PORT>> -a <<ACCESS_SERVER_ID>>
8. If you get this message “AccessGate installed Successfully.” then the Access Gate installation is successful. Otherwise verify the input parameter values for the above issued command.
9. Set the following environment variables. Set PATH to %PATH%;%ACCESS_SDK_INSTALL_DIR%/oblix/lib. Set CLASSPATH to %ACCESS_SDK_INSTALL_DIR%/oblix/lib/jobaccess.jar. Set OBACCESS_INSTALL_DIR to %ACCESS_SDK_INSTALL_DIR% .
10. If you are using Linux environment, set additional environment variable LD_LIBRARY_PATH to %ACCESS_SDK_INSTALL_DIR%/oblix/lib.
11. Make sure that Access Server SDK and JDK are of the right versions. For eg., if the JDK is 64-bit and Access Server SDK is 32-bit, then java code execution will fail.

Testing:

If you want to test a stand-alone java code download the JAccessClient.java from section 4.1 in this documentation and place it in a directory.

1. Goto java code directory. Compile the javacode using javac JAccessClient.java.
2. If there are any compiler errors and if it throwing error while compiling com.oblix.access class files, then jobaccess.jar is not placed in CLASSPATH properly.
3. Run the javacode using java JAccessClient.

If your custom application is deployed in an application Server (say Tomcat) then embed the OAM API code and set the environment variables in Application Server Startup scripts. If you are writing the code in a Java Editor such as Eclipse, make sure to add the jobaccess.jar present in %ACCESS_SDK_INSTALL_DIR%\oblix\lib in the  application classpath.