Question

3
Replies
139
Views
Rama Biswal (RCBiswal)
Total System Services

Total System Services
US
RCBiswal Member since 2013 1 post
Total System Services
Posted: October 1, 2015
Last activity: October 7, 2015
Posted: 1 Oct 2015 21:34 EDT
Last activity: 7 Oct 2015 21:20 EDT
Closed

Issues in managing Pega and IAC thru WebSeal Standard junctions

We are trying to achieve SSO thru IBM WebSeal, we could able to do so for Pega application using Transparent Junctions. For example, if our external URL is www.abc.com, then we could able to achieve SSO by routing traffic to F5 LB VIP (for example 10.1.1.1 which finally became 10.1.1.1/prweb/*. But we have requirement for IAC implementation along with Pega application on same host/domain name, but to achieve this, we may not be able to by using transparent junctions on same webseal instance, hence we may need standard junctions. For example, www.abc.com for Pega application that will go to F5 LB VIP like 10.1.1.1/prweb/* and www.abc.com/iac that will also go to another F5 LB VIP like 10.1.1.2/prweb/*, but we are failing do so as we are having to some AJAX issues. Can you please guide us if we can use standard junctions for this scenario and how? 

Also, we are thinking about deploying prweb.ear file with different context path, such as for Pega application, it will be deployed as default prweb context and for IAC we want to deploy prweb as IAC as context path. WIll this work?

Please let me know if you need any further details.

User Experience Security
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.