Hi Ken .
Logout URL - that is not the root cause here since it is used to redirect the logout mechanism of OAM secured application to a specific (custom page) . By default it shows the OAM logoff page , that behavior can be changed with this value .
Now , to the core issue . Can you provide some more details on what is the web server being used as front-end for WCC . Is it OHS or Apache ?
On the OAM side under protected resources - what all resources (pertaining to WCC ) are added ?
under Public resources - what all resources (pertaining to WCC ) are added ?
Are there any config.cfg entries on WCC related to OAM ?
Hi Ken ,
I think the reason why you are seeing the issue is the value set for :
Logout Redirect URL
where the end_url is pointing to a "resource" under WCC (which after logout is not having credentials)
I believe you should have the following set instead of the above value to see the right behavior :
did not use the https one intentionally .
Save the changes on OAM side , restart OHS and then test .
What this will do is bring up the CS Login page after logout (be it "time out" or "manual log out" ) , from where the users would be able to do normal ucm login and be authenticated correctly .
Now , if you do not want to show the CS login page post-logount , then change the end_url to show the OAM login page which would be :
Let me know how this works out .