Changing Portal (Spaces) From Private To Public and Vice Versa Is Not Propagating To All Cluster Members
(Doc ID 2148141.1)
Last updated on AUGUST 13, 2018
Applies to:Oracle WebCenter Portal - Version 18.104.22.168.1 and later
Information in this document applies to any platform.
When we make changes to access, such as Private to Public or vice-versa these changes don't make it to all members of the cluster. Also when a new Public Space is created it consistently creates the Space on some of the managed servers as Private.
Restarting the managed server process that come up in the wrong access type causes them to show as Public, the correct access type.
We just upgraded from 22.214.171.124.0 to 126.96.36.199.1 and we don't recall having this issue in the previous version.
They are using JOC, and OID as policy and credential store
There are no errors seen, just either seeing the Space (when they shouldn't be) or seeing OAM login when they shouldn't be, on the managed servers having the issues.
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