Sunny Goel

@dcasavant @PegaBasis , Can either of you please help us here ?

@dcasavant , Thanks for your response. There are 2 scenarios - Scenario # 1 -> Push the custom TLS certificate at either Load Balancer or Traefik(if used as ingress controller)...

@dcasavant , for 2nd scenario we can certainly extend the Pega Docker image to import the TLS cert of backend APIs. Let's say we do it 1st time and after...

Thanks @dcasavant

Hi @ozairs , I'm getting same issue while running api locally on MicroGateway. Tested via. Soap UI, Postman, curl but same result. Verified Client id, secret, URI etc. and everything...

Thanks @jgeddes2001 .. It's working fine for me as well.

Hi @jgeddes2001 , I'm facing the same issue with API Connect v 5.0.8.3 I tried the workaround you mentioned above in this thread but that didn't work for me. Here's...

@saywow , Thanks for your response. It means, I'll need to downgrade the Node and npm version on my machine. I'll give it a try and let you know how...

Hi @smartmouse , I was using 8.x , downgraded that to v 6.x and tried installing the APIc toolkit afterwards. But install itself is failing now. So I'm thinking to...

Even I'm unable to start following. I'm also running toolbox on windows machine. Were you able to resolve the issue? nginx microgateway ibmportal microservice