Configuring OTP through Email using OAM Adaptive Authentication Service
This post explains the steps for configuring OTP through Email using OAM Adaptive authentication Service . The OAM Oracle Adaptive service uses SOA User Messaging Service for sending the notification. Hence you need to have SOA server configured to UMS for enabling this feature.
Issue : OAMIdentityAsserter is missing in Weblogic providers
If the weblogic server 11g is installed without any Fusion Middleware components , then OAMIdentityAsserter will not available in the provider lists
This post explains the steps to fix the error , WebGate: Winnt_accept: Getsockname Error On Listening Socket, Is IPv6 Available? error .
After installing and configuring webgate 184.108.40.206 for OHS 220.127.116.11 , the below errors where displayed on the Ohs logs while starting the ohs server.
This post explains the steps to fix the error,
SEVERE:java.security.AccessControlException: access denied (oracle.security.jps.service.credstore.CredentialAccessPermission context=SYSTEM,mapName=OAMAgent,keyName=SDKAgent11g read
The complete error message is given below, Continue reading
Email Notification not working for OTP through Email option in Adaptive Authentication Service
After configuring Second Factor Authentication, the end user receives the following error after selecting the email to complete the Second Factor Authentication:
“System error. Please re-try your action. If you continue to get this error, please contact the Administrator.”
This post explains the steps to fix the error “OAMSSA-20005: Error initializing User/Role API : Identity Provider Configuration not found” while configuring Adpative Authentication Service in OAM.
After configuring the Second factor authentication in Adaptive Authentication Service, user is redirected to error page after first level authentication.
OAMSSA-20005: Error initializing User/Role API : Identity Provider Configuration not found error message is displayed in OAM logs. Continue reading
The following error message is displayed in the OAM mananged server logs while testing the OAM access client program.
oracle.security.am.asdk.OperationNotPermittedException: OAMAGENT-02005: Operation not permitted on this server.
This post explains the steps to enable Auditing in Oracle access manager 11g to database. The overview of auditing in Oracle Access Manager 11g is explained here. By default the auditing information will be stored in the bus-stop file. Follow the below steps for Oracle Access manager auditing to database.
This post explains the basics of Auditing in Oracle Access Manager 11g and also explains the run time events you can audit by enabling auditing in Oracle Access Manager 11g.
By enabling the auditing in Oracle Access manager you can track the user events like user authentication (authentication attempt, authentication success, authentication failure etc.) and authorization events (authorization success, failure etc.) Also you can track the Administrative events also by enabling auditing in Oracle Access Manager. For more details related to the OAM events that can be audited, please check the oracle documentation link here.
This post explains how to export and import policy data of OAM11gR2. Using the WLST Scripting tool we can export and import policy data of Oracle Access Manager (OAM). The steps for exporting and importing policies of OAM11gR2 is given below,
Steps for Export and Import policy data of OAM11gR2
Export OAM Policy data
The policy export scripts will export Authentication Schemes, Host Identifiers and Application domains etc to the temporary xml file .