OAM - Running of several WLST commands decrease the version in "oam-config.xml" and previous settings in "oam-config.xml" are reverted

(Doc ID 2362138.1)

Last updated on FEBRUARY 21, 2018

Applies to:

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

Symptoms

Running of several WLST commands decrease the version in "oam-config.xml" and previous settings in "oam-config.xml" are reverted.

What is happening:

(in this case we used below 2 WLST commands - but can be reproduced with other commands that modify entries in "oam-config.xml" also )

1. - Starting from "oam-config.xml" with version 100

2. - Running 2 "configTrustedInputs" WLST commands:
  - configTrustedInputs(name="DEFAULT_HEADER",maxSize="7003")
  - configTrustedInputs(name="DEFAULT_PARAMETER",maxSize="703")

3. - As expected, "oam-config-xml" version became 102

3b. - Also, as expected, settings for "DEFAULT_HEADER" and "DEFAULT_PARAMETER" appear in "oam-config.xml"

4. - Now, run WLST command "putStringProperty":
  - putStringProperty("/spglobal/samlrequestissuernamequalifier","http://abc.abc").

5. - Suddenly - version in "oam-config.xml" decrease to 101 (instead of the expected value - 103)

5b. - Also, settings for "DEFAULT_HEADER" and "DEFAULT_PARAMETER" DISAPPEAR from "oam-config.xml"


        ---------> As said, this is happening in combination with other WLST commands that modify entries in "oam-config.xml" !

This behavior is also observed in OAM Admin logs:

       -----------> first run of "configTrustedInputs":
............

[2017-12-14T13:52:09.011+01:00] [ZAmS112_S1] [NOTIFICATION] [OAMSSA-08072] [oracle.oam.config] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ......] [ecid: ......] [APP: oam_admin#11.1.2.0.0] Applying configuration update at path /DeployedComponent/Server/NGAMServer/Profile/Security. Current version of configuration 100. Change initiated on this node: true

.........

[2017-12-14T13:52:19.808+01:00] [ZAmS112_S1] [NOTIFICATION] [OAMSSA-04051] [oracle.oam.foundation.access] [tid: Configuration Store Observer] [userId: <anonymous>] [ecid: .......] [APP: oam_admin#11.1.2.0.0] Listener in ZAmS112_S1, Thread Configuration Store Observer before lock, dist version 101 config version 101.
........

        -----------> second run of "configTrustedInputs":
.........

[2017-12-14T13:58:15.286+01:00] [ZAmS112_S1] [NOTIFICATION] [OAMSSA-08072] [oracle.oam.config] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId:.......] [ecid: ........] [APP: oam_admin#11.1.2.0.0] Applying configuration update at path /DeployedComponent/Server/NGAMServer/Profile/Security. Current version of configuration 101. Change initiated on this node: true

..........
[2017-12-14T13:58:19.806+01:00] [ZAmS112_S1] [NOTIFICATION] [OAMSSA-04051] [oracle.oam.foundation.access] [tid: Configuration Store Observer] [userId: <anonymous>] [ecid: .......] [APP: oam_admin#11.1.2.0.0] Listener in ZAmS112_S1, Thread Configuration Store Observer before lock, dist version 102 config version 102.
.......

-----------> run of "putStringProperty":
..............

[2017-12-14T14:02:17.891+01:00] [ZAmS112_S1] [NOTIFICATION] [] [oracle.oam.config] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: .....] [ecid: .......] apply prop at:DeployedComponent/Server/NGAMServer/Profile/STS/spglobal/samlrequestissuernamequalifier at version:100

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms