We are using OIDC authentication. During First time log in it is working fine, but after some time it is asking for re authentication. After giving the credentials it is failing and the error shown as
”message":“Open ID ConnectConnect Flow failed, AuthService : Ping, ErrorMessage : Cannot invoke \“java.util.Map.get(Object)\” because \“ssoAttrValues\” is null””.
The failure is happening because, during re-login, Pega is expecting OIDC user attributes from the UserInfo and claim-mapping step, but Ping is returning no mapped attributes, so ssoAttrValues becomes null and the login flow stops. Pega’s OIDC operator mapping depends on attributes returned by the UserInfo provider, and Ping returns those claims based on the scopes and OIDC policy configured for the client. Reconfigure the Ping OIDC client used by Pega so the re-authentication flow always sends the same required claims, especially the operator ID claim and any fields used in your pre-auth or post-auth mapping, with the needed scopes such as openid profile email enabled. Then make sure those same claims are mapped in the Pega OIDC authentication service. Once the same claim set is returned on re-login, the authentication should work normally again.