Question

5
Replies
7549
Views
TSUCK Member since 2010 123 posts
PEGA
Posted: 4 years ago
Last activity: 4 years 4 months ago
Closed
Solved

How to get value in HTTP Header for Single Sign On

Hi,

I am trying to implement integration with WebSeal SSO in Pega 7.2. Although we may face many WebSeal-specific issues later, at this point I am trying to figure out something SSO-generic. I would like to simply get a value which is being sent over from SSO in the HTTP Header. The actual message is:

15:08:48.231416425      131.6.211.27    170.88.47.153   35014555253835653320      39389   8192    PUSH | ACK      GET /prweb/WebSealServlet/jgCtzSLC0ErkB66VLLKO0h6C6-9u0Xb4*/!STANDARD

HTTP/1.1..accept: text/html, application/xhtml+xml,*/*..accept-language: ja-JP..host: cbkvn153:8192..iv-user:X0000009..user-agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1;Trident/5.0)..via: HTTP/1.1parpdw12.aaaregression.myco.jp:443..iv_server_name:7-webseald-parpdw12..Cookie:Pega-RULES={atn}e3ByfXR4L3RpTno0OGhpdVNzbVhLMkdUY0xlbjd2eUVjL2lIR0FyZ05va2RsbTVoYjVwYVJCb0JJSFE3dmxCN0s1N0dGM3FJSERvci9tVkQKT1M1cmh2dFg2dz09;JSESSIONID=AllWSYzqETvK58eRvANVcajRN71tXuvvKbLfCpkUSodcN6keCC88!1080822193....

 

"iv-user" is the key name and "X0000009" is the actual value for ID. I found a PDN article and I guess I should be doing something like this in my custom activity https://pdn.pega.com/how-configure-sign-using-ibm-webseal-and-tivoli-access-manager

javax.servlet.http.HttpServletRequest req = (javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getProperty("pxHTTPServletRequest").getObjectValue();

UserIdentifier = req.getHeader("iv-user");

 

But I am not quite sure if this is right way (this article is old and this activity is PRExternal base which is already deprecated) or do I need to do differently. I wanted to check with someone who has done it with 7.x. Please see the excel file (WebSealSSOWithPega7.2.xlsx) attached for the details.

 

 

Thanks,

 

Kensho

Pega Platform 7.2 Data Integration
Moderation Team has archived post
Share this page LinkedIn