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 Siddhant Suryakant Jivane for achieving the title of Participant of the Week! Siddhant believes in sharing knowledge. He proved to be an amazing participant by writing a knowledge share article on a topic that will be informative to the diverse audience in the community. Read his article here. 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.
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...
Hi, Thank you for your answer but could you provide me some more precisions: In fact I have seen in my PEGA Designer Studio the status "Critical HotFix Missing" = 0 which is good. But I am running the hotfix scan (prpcServiceUtils.sh command...
Hello, Please navigate to https://community1.pega.com/digital-delivery. 8.3.1 is showing as available for download per the attached screenshot. If you still face issues please reach out via Direct Message and I will assist further. Thank you, Brodie
Please wait while we search for PDN content that suits your question.