Login Issue using external authentication(screen not loaded or not able to login)

General
,
1

The user is attempting to log in via external authentication, but upon successful login, they encounter a blank screen with a bar at the top. We have examined both the server log and the Pega log but could not find any relevant information. We have also implemented logging related to OIDC (OpenID Connect), and it appears that the token is being validated correctly. After verification, the user is directed to the Operator ID page, following the model operator check.

This issue is occurring for both existing and new users, although some users can log in without any problems. Do you have any insights into what might be causing this issue? It’s important to note that we are using the Tomcat server.

2

@Sutanu a search on the PSC brought me to a similar post here:

After successful SSO login, user is directed to Pega Login page

This issue might be related to the version of Tomcat you are using. If your instance is running on Tomcat 8.5.42 or below, it requires certain DSS settings.

You should apply the following DSS and restart the server:

Owning Ruleset: Pega-Engine

Purpose: prconfig/authentication/usepreauthenticationcookie/default

Value: false

Also set the below:

security/csrf/samesitecookieattribute value = None

prconfig/http/setsecurecookie/default = true

prconfig/authentication/redirectguests/default = False

This sounds like a valid GCS support ticket.

If you have no further help on this forum feel free to log an incident via the MSP and please provide the INC id here so that we can help track it.

3

@MarijeSchillern Thanks a lot for your response. We have raised an incident and its resolved now.

Root Cause was a netscaler security update.

4

@Sutanu please can you provide the INC ticket id reference here?

I believe it was INC-B2932 and the full explanation from the Netscaler team was a problem with their security patch that causes the issue in pega which stopped the script to run due to cookie changes. Issue was resolved after they modified security policies to not block pega scripts.