Below is the lists all the error message codes sent by the OAM Server and the corresponding primary error message. If a primary error message has been customized for an application, the application must map this custom message to the corresponding standard error message maintained by OAM Server. There is no difference between OAM-1 and OAM-2 error codes. Continue reading “OAM Error Codes”
List of protected, public and excluded resources including WebCenter, SOA and Content. This is for 126.96.36.199.0
When you use the Oracle Access Manager Identity Asserter, all web.xml files in the application EAR file must specify CLIENT-CERT in the element auth-method for the appropriate realm.
You can add comma separated values here when you want applications accessed directly over the WebLogic Server host:port to be authenticated by the container. For instance:
The auth-method can use BASIC, FORM, or CLIENT-CERT values. While these look like similar values in Oracle Access Manager, the auth-method specified in web.xml files are used by Oracle WebLogic Server (not Oracle Access Manager). Continue reading “Application configuration for OAM Integration”
With Oracle Access Manager 11.1.1, the Embedded Credential Collector (IECC) is the default. The ECC was and is integrated with the OAM Server. Continue reading “About 11g Webgate Configured as a Detached Credential Collector”
The request flow when a user requests access is as follows: Continue reading “Overview of User Request when OAM is configured”