OAM 11g: Regenerating osso.conf through the Oracle Access Manager Console Causes Internal System Error
(Doc ID 1485727.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
After installing the Oracle Access Manager 11g (OAM 22.214.171.124) and running the upgrade assistant...
... needed to make a change to the port and protocol within the OAMServerProfile tag in the oam-config.xml file.
- Modified the migrated OSSO agents using the OAM Console UI
- Copied the newly generated osso.conf files to parnter apps side
- Bounced parnter apps
- Testing the mod_osso applications, redirects to the oam login screen...
... but instead of presenting with a username and login, a system error is displayed ...
System error. Please re-try your action. If you continue to get this error, please contact the Administrator.
- Errors in oam_server1-diagnostic.log:
...[oam_server1] [NOTIFICATION] 
Regenerated osso.conf files through OAM console
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|