Changes made through /share/page/modules/deploy are not propagated to other nodes in the cluster.
Steps to reproduce:
1 Setup a two node ACS 6.2.2 cluster
2 Install the SAML module on both nodes and enable but not enforce SAML so there will be a link to the IDP on /share/page
3 Go to node 1 http://localhost:8080/share/page/ the link to the IDP is displayed
4 Go to node 1 /share/page/modules/deploy
5 Remove the SAML module
6 Apply the changes
7 Go to node 1 http://localhost:8080/share/page/ the link to the IDP is not displayed
8 Go to node 2 /share/page
The link to the IDP is displayed
The link to the IDP is NOT displayed
The Modules with configurations are saved in the repository but they are never read on the other cluster node, since the modules are "cached" in the ModuleDeploymentService.
When changing settings (under /share/page/modules/deploy), ModuleDeploymentService.setDeployedModules gets executed but does not call updateClusterCache.
updateClusterCache would send a message to the other nodes in the cluster to invalidate the module Cache and in subsequently reload the module modified configurations persisted in the repository.
Customer fixed the behaviour by extending the ModuleDeploymentService and issuing updateClusterCache at the end of setDeployedModules.