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

 Sari Abdel-Latif (Sari.alatif)
Rulesware

Rulesware
CA
Sari.alatif Member since 2015 5 posts
Rulesware
Posted: Dec 3, 2019
Last activity: Dec 15, 2019
Posted: 3 Dec 2019 17:28 EST
Last activity: 15 Dec 2019 22:08 EST
Closed

Auth0 Implementation over PegaCloud

Hello,

my client is transitioning to Auth0 over OIDC (OpenID connect) implementation for their SSO needs.

I'm working on a proof of concept to build the Authentication service for this, and came across this quite helpful article ( Authenticating to Pega with Auth0 using OIDC protocol | Pega Community ) ,after configuring the service, and verifying all information. I've enabled it.

But going to the login URL provided :

Show More

Hello,

my client is transitioning to Auth0 over OIDC (OpenID connect) implementation for their SSO needs.

I'm working on a proof of concept to build the Authentication service for this, and came across this quite helpful article ( Authenticating to Pega with Auth0 using OIDC protocol | Pega Community ) ,after configuring the service, and verifying all information. I've enabled it.

But going to the login URL provided :

https://CLIENT.pegacloud.net/prweb/PRAuth/Auth0
I keep being rerouted to
https://CLIENT.pegacloud.net/prweb/
The article doesn't mention anything about a web.xml update, is that needed similar to other authentication approaches ?
i.e. create a servlet / servlet mapping and update web.xml ?
Thanks,
-Sari

***Edited by Moderator Marissa to update platform capability tags****


Show Less
To see attachments, please log in.
Cloud Services
Security

Posted: 5 years ago
Posted: 15 Dec 2019 22:08 EST
Sari Abdel-Latif (Sari.alatif)
Rulesware

Rulesware
CA

Hello,

Checking the current environment, the web.xml itself is customized and seems the PRAuth servlet was removed. I plan to add it. However, checking other default Pega 8.x installations, the PRAuth servlets don't have any mention of a specific "AuthService" , is that the norm for Pega 8 ? , or do I need to update the servlet with an "AuthService" field ? 

Thanks,

-Sari 

 

PS: here is the sample I found from a default not customized installation:

Show More

Hello,

Checking the current environment, the web.xml itself is customized and seems the PRAuth servlet was removed. I plan to add it. However, checking other default Pega 8.x installations, the PRAuth servlets don't have any mention of a specific "AuthService" , is that the norm for Pega 8 ? , or do I need to update the servlet with an "AuthService" field ? 

Thanks,

-Sari 

 

PS: here is the sample I found from a default not customized installation:

<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>

Show Less
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