Oam 11G: Regenerating osso.conf Through The Oracle Access Manager Console Causes Internal System Error
(Doc ID 1485727.1)
Last updated on OCTOBER 24, 2019
Applies to:Oracle Access Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
After installing the Oracle Access Manager 11g (OAM 188.8.131.52) 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_SERVER_NAME>-diagnostic.log:
...[<OAM_SERVER_NAME>] [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