Reply posted on January 15, 2020 by SiddhantJivane
Future: adaptation of Dockerization and Container Orchestration.
Collaborate with developers, support engineers, and experts who build and work with Pega products and services. Join us to get fast answers to your questions, and participate in our Ask the Expert sessions!
Congratulations to Basil Pozdeev for achieving the title of Participant of the Week! Basil proactively assisted several users with their queries, which helped them progress with the troubleshooting and build successful solutions. We appreciate your efforts to share knowledge in the community. Hope to see you around and keep up the great work!
Just an update, based on the resolution provided by the engineering team after changing the signing algorithm of the ID Token to asymmetric keys we were able to get the SSO working. ie, changing from HS256 to RS256.
Added new Rule set to application. This resolved the issue. Thanks.
Hi, We are trying to configure pega authentication via oidc auth service, but we getting the following error:com.pega.pegarules.pub.PRRuntimeException: Unable to execute OIDC flow: Received invalid status code 401 I think it might occur because of 16...
Please refer https://community.pega.com/knowledgebase/articles/migrating-android-custom-mobile-apps-use-push-notifications-firebase-cloud for 7.* instances, as it contains instructions and list of HFix'es for different 7.x versions. Not sure why...
Please wait while we search for PDN content that suits your question.