Cannot register applications with process fabric - 403 error - all in same instance

I cannot register my applications on process fabric. When I do I get this error

“(PPF-Work-Registration)Failed to connect - the HTTP response code of 403 indicated a client error. The response data may contain a reason. // The body of the service’s response, which is set up for mapping in the Connector rule, was empty for this service call.** Response”

I know its not an incorrect client id or secret because if i use the wrong password I get a 401 instead.

When I try and trace the service …/prweb/api/ppfconnect/v1/apps I get nothing as it’s failing before it hits the service. However in the logs I have the following

“Rest service [ppfconnect][v1][apps9a6dd283c3de653fbca500f9721f634f] failed:Authorization failed, please contact system administrator.:com.pega.pegarules.pub.services.ServiceException: Authorization failed, please contact system administrator.”

I’ve believe that I have set it up correctly as I have done the following

  • Updated the PPFConnect keystore to have the url of the current instance
  • Updated the service package ppfconnect to use the access group of the application I am trying to register
  • Updated the token profile PPFConnect to use the truststore PPKFS as PPF and the application are running on the same instance.
  • Updated the truststore PPKS with a kestore file with certs
  • Updated PPFToRemoteTokenGeneration to use the truststore PPKS
  • Updated the DSS PegaProcessFabricSvcURL to have the current instances url
  • Updated the DSS AllowedRegistrationAccessGroups to have the access group of the application I am trying register
  • Created an OAuth Client

I’m at a bit of a loss.

@MatthewH5221 Hi,

As per the below screenshot it seems that the component is missing in the application which you are trying to connect can you please check and confirm if that is available

Also please have a look at the below article to check if any of the given trouble shooting options helps

Troubleshooting