This related to INC-167764, OIDC isn't working for us because the ID provider is encrypting the token using "SHA-512" This can't be decoded by Pega right now, and we really need to support this for all external users.
***Edited by Moderator Marissa to update Support Case Details; edit INC and remove hyperlink***
I am handling the INC-1677764 from GCS side. Client's external OIDC provider is using "HMACSHA512" symmetric key encryption. Engineering team has confirmed that we support only asymmetric signing of IDTokens. Symmetric signing and encryption of IDTokens are not supported as of now. Checking to see when this will be supported in the future releases?
Posted: 1 month ago
Posted: 14 Jun 2021 4:05 EDT
Pooja Gadige (PoojaGadige)
Technical Documentation Specialist
Thank you for sharing your idea here in the Pega Collaboration Center (PCC)!
I have submitted this idea on your behalf in our internal system for feature enhancements and updated your post with the associated FDBK-ID. You can take this ID to your Account Executive for next steps.