What Motivates You to Participate Here in the PSC?
Reply posted on June 12, 2019 by JaikumarND
Hi Kevin- Thanks for the reply. The container error we fixed at the 1st pace itself (it was self explanatory) and is not an issue any more. There are other exceptions in the log file.
Reply posted on June 10, 2019 by teeguPega
You need to login with a specific operator which assigned for deployment manager. we can't login with all the operators. after installing the jar few operators will be added. try to login with those operators
Reply posted on May 30, 2019 by gurrp1Pega
Issue looks to be with credentials provided to connect to Jenkins. Please verify auth profile provided in pipeline configuration to connect to jenkins.
Reply posted on May 26, 2019 by ROBERTSD
Hi Vijay, Did you get any updates on this?. I am looking for a similar approach in case archiving too. S3 bucket has a flat storage structure so wanted to get information on how a case is stored there.
Reply posted on May 16, 2019 by ramap2Pega
<instanceID> is the <entityID> in the SAML2 terminology. This is auto-generated and can be found as label Entity identification in the Service Provider(SP) settings of the pega authentication service configuration.
Reply posted on May 13, 2019 by Vibek_SharmaPega
Hi Brian, Please find the answers. 1. Why do we need the access key and secret key? 2. What purpose do they serve? We need these details to identify to which user this S3 bucket does belong to, secondly does the user have authenticated access to the S3...
Reply posted on May 12, 2019 by Abhinav7Pega
Hi, Azure is a cloud computing service.Pega's installation does not depends on cloud service but It is specific to database,server and version.Please find below installation guide for pega 8.2,tomcat and oracle. https://community.pega.com...