2-38 Developers Guide for Oracle Access Manager and Oracle Security Token Service
■
ObAccessRuntimeException : This class indicates a runtime error while
performing operations that use ObAuthenticationScheme and ObResourceRequest classes.
2.8.3 Deprecated: Oracle Access Manager 10g JNI SDK
The Access SDK provides support for interfaces in the 10g JNI ASDK com.oblix.access package. However, all APIs in com.oblix.access are marked as deprecated. These
APIs will not be enhanced or supported in future Oracle Access Manager 11g Access SDK releases.
2.9 Migrating Earlier Applications or Converting Your Code
This section describes the migration processes to follow if you want to use the Access SDK. Migrating to the Access SDK can be necessary for the following reasons:
■
Migrate applications to replace the com.oblix.access API of Oracle Access Manager 10g JNI ASDK with the corresponding API in Oracle Access Manager 11g
Access SDK without changing how those applications use Access SDK.
■
Migrate application code to use oracle.security.am.asdk API instead of com.oblix.access, which is supported in Oracle Access Manager 11g Access
SDK for backward compatibility.
This section contains the following topics:
■
Modifying Your Development and Runtime Environment
■
Migrating Your Application
■
Converting Your Code
2.9.1 Modifying Your Development and Runtime Environment
Before migrating an application, ensure that your development environment is configured. Also ensure that the Oracle Access Manager 11g Access SDK is configured
correctly. For more information, see Section 2.5, Configuring and Deploying Access
Clients .
2.9.2 Migrating Your Application
You can migrate Access Clients and plug-ins developed with the Oracle Access Manager 10g com.oblix.access package to operate with the OAM 11g Server. This
section describes how programs written with the Oracle Access Manager 10g JNI ASDK can be used with Oracle Access Manager 11g.
Support for the classes and interfaces provided in Oracle Access Manager 10g JNI SDK and in Oracle Access Manager 11g Access SDK is identical.
In general, you are not required to change or recompile any application code when migrating applications to use com.oblix.access classes from Oracle Access
Manager 11g Access SDK.
Note: For information about the similarities and differences between
the com.oblix.access APIs in Oracle Access Manager 10g JNI and in Oracle Access Manager 11g Access SDK, see
Section 2.8.2, Compatibility of 10g JNI ASDK and 11g Access SDK
.
Introduction to the Access SDK and API 2-39
A new runtime exception, ObAccessRuntimeException, was introduced in the com.oblix.access package. Oracle Access Manager throws this exception when
performing operations of AuthenticationScheme and ResourceRequest classes.
Oracle recommends that you perform proper exception handling in the application code. If this is done, the application should be recompiled with the OAM 11g Access
SDK jar file.
2.9.2.1 Configuration Specific to Migration
This discussion assumes that Oracle Access Manager 10g ASDK component is installed and configured with the OAM Server. This scenario uses existing Access
Client applications developed using Oracle Access Manager 10g JNI ASDK. The following assumptions are made:
■
The configuration items listed in Section 2.5.1, Configuration Requirements
are referenced from the Oracle Access Manager 10g ASDK installation directory
ASDK_INSTALL_DIR.
■
ObAccessClient.xml is read from ASDK_INSTALL_DIRaccessoblixlib.
■
password.xml is read from ASDK_INSTALL_DIRaccessoblixconfig if the transport security mode is Simple or Cert.
Simple Mode To configure the Oracle Access Manager 10g ASDK component in Simple mode, see
the Oracle Access Manager Administration Guide for the 10g release.
Perform the following steps:
1.
Import the aaa_cert.pem and aaa_key.pem files into oamclient-keystore.jks. The aaa_cert.pem and aaa_key.pem files are located in ASDK_INSTALL_
DIRaccessoblixconfigsimple.
2.
Located the self-signed CA certificate used for issuing Simple mode certificates in ASDK_INSTALL_DIRaccessoblixtoolsopensslsimpleCA.
3.
Import the self-signed CA certificate into oamclient-truststore.jks.
4.
Import the certificate and key files into the JKS store by following the steps in Section 2.5.3, SSL Certificate and Key Files
.
5.
Copy the JKS stores to ASDK_INSTALL_DIRaccessoblixconfigsimple.
Cert Mode To configure the Oracle Access Manager 10g ASDK component in Cert mode, see the
Oracle Access Manager Administration Guide for the 10g release.
Perform the following steps:
1.
Import the aaa_cert.pem and aaa_key.pem files into oamclient-keystore.jks. Import the aaa_chain.pem into oamclient-truststore.jks.
The aaa_cert.pem, aaa_key.pemand aa_chain.pem files are located in ASDK_ INSTALL_DIRaccessoblixconfig.
2.
Import the certificate and key files into the JKS store by following the steps in Section 2.5.3, SSL Certificate and Key Files
.
3.
Copy the JKS stores to ASDK_INSTALL_DIRaccessoblixconfigsimple.
