When accessing the Oracle Access Management Console, the WebLogic Server (AdminServer) host and port must be specified in the URL.
Let's assume the following sample URL, https://wlsadminhost.example.com:7001/oamconsole. In this URL, the following is true.
HTTPS represents the Hypertext Transfer Protocol (HTTP) with the Secure Socket Layer (SSL) enabled to encrypt and decrypt user page requests and the pages returned by the Web server
wlsadminhost.example.com refers to fully-qualified domain name of the computer hosting the Oracle Access Management Console (AdminServer)
7001 refers to the designated bind port for the Oracle Access Management Console, which is the same as the bind port used for AdminServer (the WebLogic Server Administration Console)
/oamconsole/ refers to the Oracle Access Management Console Log In page
If you specify an OAM Server host and port (as you would to access the ODSM console), the AdminServer redirects to the managed server which produces a ‘404 Not Found’ error.
When navigating to the /oamconsole URL, the default Oracle Access Management Console login page is displayed. The following sections have details on logging into the Oracle Access Management Console.
Ensure that you use the correct administrative credential to log in. Initially, the LDAP group for the Oracle Access Management Console Administrator is the same as the LDAP group defined for the WebLogic Server Administration Console (
Administrators) and the common Default System User Identity Store store is the WebLogic Embedded LDAP.
With appropriate administrative credentials, you can log into the Oracle Access Management Console.
Use this procedure to log in to the Oracle Access Management Console.
Oracle Access Manager (OAM) renders a login page on accessing an application protected by OAM. System Administrators can specify where they want to redirect the user to, if the user has bookmarked the login page. They can specify any protected resource URL as the default page under Challenge Parameters field of the authentication scheme. The login page URL will contain a context to locate the landing page. When a bookmarked login page is accessed , OAM server will redirect the user to the default login page defined in the authentication scheme that is tied to the login page.
Following is an example to set Challenge Parameter in Authentication scheme:
In the above example
landingpage.html will be defined as a protected resource and
oam11g is the host identifier.
The following Oracle Access Manager server behavior is pertinent on accessing a bookmarked login page:
Oracle Access Manager server will redirect the user to the default login page defined in the authentication scheme that is tied to the login page.
If there is no default page defined in the authentication scheme that is tied to the login page, then Oracle Access Manager server will redirect the user to the default login page defined in the default authentication scheme.
If there is no default page defined both in the authentication scheme that is tied to the login page and the default authentication scheme then the following error message will be seen:
System error. Please re-try your action. If you continue to get this error, please contact the Administrator.
Note:Bookmarked login page contains a query parameter named ‘bmctx’. The parameter and its value are required to be submitted to the oam server when login credentials are submitted.
To go into the Secure Oracle Access Management Console (HTTPS):
$ cd $MIDDLEWARE_HOME/wlserver_10.3/server/lib/
-list command prints the contents of the keystore for reference. DemoIdentityKeyStorePassPhrase is the default password for the keystore DemoIdentity.jks.
$ keytool -list -keystore DemoIdentity.jks -storepass DemoIdentityKeyStorePassPhrase $ keytool -exportcert -keystore DemoIdentity.jks -storepass DemoIdentityKeyStorePassPhrase -alias demoidentity -file ~/demoidentity.cer
cd $DOMAIN_HOME/config/fmwconfig/ovd/default mkdir keystores cd keystores $ keytool -importcert -keystore adapters.jks -storepass New_Password -alias demoidentity -file ~/demoidentity.cer
$ keytool -list -keystore ./adapters.jks -storepass New_Password
vim server.os_xml server.os_xml: <keystore>keystores/adapters.jks</keystore> server.os_xml: <trustStore>keystores/adapters.jks</trustStore> <trustStore>keystores/adapters.jks</trustStore> <trustStorePassword>New_Password</trustStorePassword>