Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Naveen Mandapati (NaveenM4274)
Tech Mahindra
Lead System Architect
Tech Mahindra
CA
NaveenM4274 Member since 2014 17 posts
Tech Mahindra
Posted: Apr 21, 2017
Last activity: Apr 23, 2017
Posted: 21 Apr 2017 9:31 EDT
Last activity: 23 Apr 2017 23:52 EDT
Closed
Solved

Unable to build SAML2 Logout Response Redirect URL

Hi All,

Show More

Hi All,

Am running into an issue with SAML log out,

2017-04-20 14:12:15,627 [ WebContainer : 2] [ STANDARD] [ ] [ CBR:01.01.01] ( internal.mgmt.Executable) ERROR prpc-dev02.ist.intralink.bns| Proprietary information hidden s8002473 - Exception
com.pega.pegarules.pub.PRRuntimeException: Unable to build SAML2 Logout Request Redirect URL : Unable to build SAML2 Logout Response Redirect URL : java.security.KeyStore$TrustedCertificateEntry incompatible with java.security.KeyStore$PrivateKeyEntry
at com.pega.pegarules.integration.engine.internal.util.PRSAMLv2Utils.generateRedirectURL(PRSAMLv2Utils.java:640)
at com.pegarules.generated.activity.ra_action_samlsinglelogoff_5173192a9453dc64a2033578a10d8d73.step2_circum0(ra_action_samlsinglelogoff_5173192a9453dc64a2033578a10d8d73.java:638)
at com.pegarules.generated.activity.ra_action_samlsinglelogoff_5173192a9453dc64a2033578a10d8d73.perform(ra_action_samlsinglelogoff_5173192a9453dc64a2033578a10d8d73.java:93)

Caused by:
com.pega.pegarules.pub.PRRuntimeException: Unable to build SAML2 Logout Response Redirect URL : java.security.KeyStore$TrustedCertificateEntry incompatible with java.security.KeyStore$PrivateKeyEntry
at com.pega.pegarules.integration.engine.internal.util.PRSAMLv2Utils.getCredential(PRSAMLv2Utils.java:789)
at com.pega.pegarules.integration.engine.internal.util.PRSAMLv2Utils.generateRedirectURL(PRSAMLv2Utils.java:627)
... 72 more
Caused by:
java.lang.ClassCastException: java.security.KeyStore$TrustedCertificateEntry incompatible with java.security.KeyStore$PrivateKeyEntry
at com.pega.pegarules.integration.engine.internal.util.PRSAMLv2Utils.getCredential(PRSAMLv2Utils.java:775)
... 73 more

https://community.pega.com/support/support-articles/logout-when-idp-does-not-provide-slo-failing-0

https://community.pega.com/support/support-articles/logout-error-saml-authentication

I tried the options provided in pdn, but i am running into new issues

1) User 1 logged in to enterprise portal and then launches PEGA from SSO SAML - clicks on a specific workbasket

2) Log off from PEGA

3) Log off from Enterprise Portal.

4) using the same browser user 2 logs in to enterprise portal and launches PEGA

5) Instead of showing default portal, User 2 is getting displayed that specific workbasket which was access by previous user.

Any thoughts, ?

Thanks
NM

***Updated by moderator: Lochan to add Categories***


Show Less
To see attachments, please log in.
Data Integration
System Administration

Accepted Solution

Posted: 7 years ago
Posted: 22 Apr 2017 10:14 EDT
Naveen Mandapati (NaveenM4274)
Tech Mahindra
Lead System Architect
Tech Mahindra
CA

As per our requirement we have to close the browser but in default pega logoff it will be redirected to login page.

you have to additionally call the below activity which will kill the session from SMA.

Call Code-Security.EndSession  with paramters PARAM.pzAuth=guest

This solved the problem.

To see attachments, please log in.
Posted: 7 years ago
Posted: 21 Apr 2017 15:03 EDT
Naveen Mandapati (NaveenM4274)
Tech Mahindra
Lead System Architect
Tech Mahindra
CA

I was going through the code and SMA then i found that browser requestor is not getting completely killed even though the tracer tells otherwise. 

SMA is showing like below.

H37CCD281A4FFAD2C83C2B11476B3FBD1 none   4/21/17 2:01:06 PM EDT Activity=LogOff

I am calling OOTB logoff, only thing i am doing different is i am auto closing window. 

 

Some pdn links

https://collaborate.pega.com/question/session-log-upon-browser-close

 

 

 

To see attachments, please log in.

Accepted Solution

Posted: 7 years ago
Posted: 22 Apr 2017 10:14 EDT
Naveen Mandapati (NaveenM4274)
Tech Mahindra
Lead System Architect
Tech Mahindra
CA

As per our requirement we have to close the browser but in default pega logoff it will be redirected to login page.

you have to additionally call the below activity which will kill the session from SMA.

Call Code-Security.EndSession  with paramters PARAM.pzAuth=guest

This solved the problem.

To see attachments, please log in.

Related content:

Question Solved

Unable to process the SAML WebSSO request : Unable to build SAML2 Logout Response Redirect URL : Failed to load SecretKeyEntry or

Question

SAML2 SSO Url questions

Question

SAML SSO: Error Message: Unable to process the SAML Web SSO request : Unable to process SAML2 Authentication response : Caught Exception while validating SAML2 Authentication response protocol : NULL

Question

SAML2 login URL not start with https

Question

Logout Redirection not working on new saml authentication service

Question Solved

Unable to process the SAML WebSSO request : Unable to process SAML2 Authentication response : Caught Exception while validating SAML2 Authentication response protocol : Caught Exception while creating Keystore instance

Question

Unable to build SAML2 Authentication request : trusted certificate entries are not password-protected

Question

Redirect the rest service response to another URL

Question

Unable to process the SAML WebSSO request : Caught Exception while validating SAML2 Authentication response protocol

Question

Unable to process the SAML WebSSO request : Caught Exception while validating SAML2 Authentication response for SSO profile

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice