My Oracle Support Banner

Oracle Access Manager (OAM) Agent Artifact Files In The DOMAIN_HOME/output/<AGENT_NAME> Directory Are Reverted To The Old Settings (Doc ID 3011905.1)

Last updated on MARCH 21, 2024

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


ObAccessClient.xml and cwallet.sso files in the DOMAIN_HOME/output/ directory is reverted to the prior settings after wls server restart

1. Using the OAM console, changes are made to the agent registration and new artifact files are generated in the output directory.

2. These artifacts are then copied to the proper location on the WebGate server.

3. Everything works as expected.

4. This is where to me it is unclear which WSL server is restarted the WLS Admin server or the WLS managed server running OAM, or both? Either was when the WLS server is restarted the artifacts in the output directory are reverted to their prior status, before the Agent registration was modified and new file created.

a. There is no loss in functionality. The WebGate in question still has the working artifact files.
b. The only issue is the agent artifact files in the output directory are reverted to the prior state.
c. If the OAM console is used again to update the Agent registration new artifacts are generated and show the most current change.
d. If after the new artifact files are created in the output directory, the WLST function “saveAccessArtifacts” is run the issue is not seen.


 Update Agent registration via the 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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.