@BRAHMESH@ As of now, Pega does not natively support the PAR (Pushed Authorization Requests) model in the OpenID Connect (OIDC) flow. PAR is an extension to the standard OIDC flow where the client sends authorization parameters directly to the authorization server via a secure backchannel before redirecting the user. Pega’s OIDC implementation mainly supports the traditional Authorization Code and Implicit flows, where parameters are passed through the browser redirect URL. If you need to implement PAR for security or compliance reasons, you would have to use a custom implementation or middleware between Pega and the Identity Provider (IdP) to handle the PAR flow and token exchange securely.