This content has been marked as final. Show 6 replies
cookie is client side and browser based. Cookie contains information like timestamp, name of domain etc.
As long as you have one Access Manager, it will set/read cookie, and between different applications, each
protected by webtier which is registered to this Access Manager.
In your case, you should have 2 different webtier, each protecting your app, and then register each webtier to
If it is the weblogic domain than what about if we have two weblogic for two different applican deployed ?
the Access Manager.
The domain is not the WebLogic domain, but the .com or .co.uk type domain. In the suggested architecture above, when you have two webtiers front-ending different WebLogic domains, you will have SSO between the two domains provided the web servers are in the same cookie domain.