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

 Azhar Hussein Syed (AzharHussein)
ATOS Syntel
Senior Consultant
ATOS Syntel
GB
AzharHussein Member since 2012 2 posts
ATOS Syntel
Posted: Sep 13, 2018
Last activity: Feb 17, 2021
Posted: 13 Sep 2018 9:31 EDT
Last activity: 17 Feb 2021 10:12 EST
Closed
Solved

SAML 2.0 SSO Implementation in 7.4

Hi, We are trying to implement SSO using SAML 2.0 authentication in Pega 7.4

We have referred to Pega help and also the below link

https://community.pega.com/knowledgebase/articles/configuring-pega-7-platform-service-provider-sp

we have created a 'SAMLAuth' Authentication rule which has autogenerated the following URL

https://XXXXXXX:53490/<context root>/PRAuth/sso

as per the article it recommends the following

"Select one of the names: SAMLAuth, SAMLAuth1, or SAMLAuth2 to use the built-in web contexts sso, sso1, or sso2, respectively"

but when we try to launch the URL we are getting following error

PegaRULES Web Application Error

Message: An has occurred processing this request. Please contact your system administrator.

PegaRULES 7.40 (PRPC-7.4.0-185)

when we change the URL to https://XXXXXXX:53490/<context root>/sso

we get the following error

Show More

Hi, We are trying to implement SSO using SAML 2.0 authentication in Pega 7.4

We have referred to Pega help and also the below link

https://community.pega.com/knowledgebase/articles/configuring-pega-7-platform-service-provider-sp

we have created a 'SAMLAuth' Authentication rule which has autogenerated the following URL

https://XXXXXXX:53490/<context root>/PRAuth/sso

as per the article it recommends the following

"Select one of the names: SAMLAuth, SAMLAuth1, or SAMLAuth2 to use the built-in web contexts sso, sso1, or sso2, respectively"

but when we try to launch the URL we are getting following error

PegaRULES Web Application Error

Message: An has occurred processing this request. Please contact your system administrator.

PegaRULES 7.40 (PRPC-7.4.0-185)

when we change the URL to https://XXXXXXX:53490/<context root>/sso

we get the following error

Caught exception: com.pega.pegarules.pub.PRRuntimeException: Custom authentication failed: invalid Data-Admin-AuthService instance: SAMLAuth

Below are the setting in web.xml for sso

<servlet>
<servlet-name>sso</servlet-name>
<display-name>sso</display-name>
<description>sso</description>
<servlet-class>com.pega.pegarules.internal.web.servlet.WebStandardBoot</servlet-class>
<init-param>
<param-name>PegaEtierClass</param-name>
<!-- COMPONENTS: This was previously com.pega.pegarules.services.HttpAPI -->
<param-value>com.pega.pegarules.session.internal.engineinterface.service.HttpAPI</param-value>
</init-param>
<init-param>
<param-name>AuthenticationType</param-name>
<param-value>PRCustom</param-value>
</init-param>
<init-param>
<param-name>StatusPage</param-name>
<param-value>/diagnostic/status.jsp</param-value>
</init-param>
<init-param>
<param-name>AuthService</param-name>
<param-value>SAMLAuth</param-value>
</init-param>
<init-param>
<param-name>RuntimeServletName</param-name>
<param-value>sso</param-value>
</init-param>
<init-param>
<param-name>SecureServletName</param-name>
<param-value>sso</param-value>
</init-param>
</servlet>
Also, the servlet mapping for SSO is follows.
<servlet-mapping>
<servlet-name>sso</servlet-name>
<url-pattern>/sso</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>sso</servlet-name>
<url-pattern>/sso/*</url-pattern>
</servlet-mapping>
Can you please suggest what is the AuthenticationType to be used in web.xml?
Also, can you please explain while creating the SAML type Auth service why is pega auto generating the URL with PRAuth servlet?
As per the web xml PRAuth servlet it mapped as follows.
<servlet>
<servlet-name>PRAuth</servlet-name>
<display-name>PRAuth</display-name>
<description>PRAuth</description>
<servlet-class>com.pega.pegarules.internal.web.servlet.WebStandardBoot</servlet-class>
<init-param>
<param-name>PegaEtierClass</param-name>
<!-- COMPONENTS: This was previously com.pega.pegarules.services.HttpAPI -->
<param-value>com.pega.pegarules.session.internal.engineinterface.service.HttpAPI</param-value>
</init-param>
<init-param>
<param-name>AuthenticationType</param-name>
<param-value>PegaAuthentication</param-value>
</init-param>
<init-param>
<param-name>StatusPage</param-name>
<param-value>/diagnostic/status.jsp</param-value>
</init-param>
<init-param>
<param-name>RuntimeServletName</param-name>
<param-value>PRAuth</param-value>
</init-param>
<init-param>
<param-name>SecureServletName</param-name>
<param-value>PRAuth</param-value>
</init-param>
</servlet>
Servlet mapping for PRAuth
<servlet-mapping>
<servlet-name>PRAuth</servlet-name>
<url-pattern>/PRAuth</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>PRAuth</servlet-name>
<url-pattern>/PRAuth/*</url-pattern>
</servlet-mapping>
***Edited by Moderator: Pallavi to update platform capability tags***

Show Less
To see attachments, please log in.
Security
Installation and Deployment

Accepted Solution

Posted: 6 years ago
Posted: 14 Sep 2018 5:39 EDT
Rajeev Ranjan (ranjr)
PEGA
Principal Technical Solutions Engineer
PEG
PL

Hi There,

1. Have you done any changes to OOTB web.xml

2. I have tried to setup the saml2 at my end and it is working as expected.

3. setting at my end:

a. Create authentication service : you can give any name. I gave saml

b. configure alias :

c.  I loged in with http:////localhost:9740/prweb/PRAuth/sso.

and it worked.

so, have you done any web.xml changes. If yes, is it possible to revert it and try in this way.

To see attachments, please log in.
Posted: 6 years ago
Posted: 14 Sep 2018 7:20 EDT
Azhar Hussein Syed (AzharHussein)
ATOS Syntel
Senior Consultant
ATOS Syntel
GB

Hi, 

Thank you for replying to this.

We have not done any changes in the OOTB web.xml. I have provided the servlet details for SSO and PRAuth in the original post (above). Can you please share the same for your web.xml (SSO and PRAuth) so that we can compare?

To see attachments, please log in.
Posted: 6 years ago
Posted: 19 Sep 2018 13:21 EDT
Marissa Rogers (MarissaRogers)
MOD
Principal Knowledge Management Specialist
Pegasystems Inc.
US

So glad that you were able to sort this out! Could you share the resolution here and we can mark it as the Correct Answer that way others who may have the same question in the future could use your resolution to solve for themselves?

Thanks!

To see attachments, please log in.
Posted: 6 years ago
Posted: 20 Sep 2018 4:49 EDT
Azhar Hussein Syed (AzharHussein)
ATOS Syntel
Senior Consultant
ATOS Syntel
GB

Hi Marissa, As suggested above by Ranjr the issue was with the web.xml configuration. When reverting it to default settings we were able to get it working.

Thank you!

To see attachments, please log in.

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