Pega Foundation for Healthcare - HTTP 401 code using OOTB Basic Authentication profile ‘CommonObjectAuthProfile’
I am using Pega Foundation for Healthcare. I am using Data Page: D_ConnectGetPlanDetails PegaHC-API:08-01-01 that uses the Connect REST : PegaHC-API GetPlanDetails. I am getting the following error:
|
pyHTTPResponseCode |
401 |
|
pyStatus |
Fail |
|
pyStatusMessage |
the server responded with an HTTP 401 code, indicating an authorization problem. // The body of the service's response, which is set up for mapping in the Connector rule, was empty for this service call. |
|
pyStatusValue |
Fail: Authentication parameters incorrect |
In Connect REST : PegaHC-API GetPlanDetails, we are using OOTB Basic Authentication profile ‘CommonObjectAuthProfile’ to configure the appropriate user credentials to be able to invoke the services that are configured to test the Plan Request with the provided in Pega Foundation for Healthcare.
I have tried suggestions from https://support.pega.com/question/401-unauthorized-error-pega-service-rest-api
but no fixes.
Any ideas for a solution?
Accepted Solution
Updated: 14 Nov 2024 16:20 EST
Pegasystems Inc.
US
@jassa I created a new AdminPCXchg Operator as a replacement in ‘CommonObjectAuthProfile’ profile. Updated password. Added Access Group: PegaHCCore:Administrators to the new Operator. Now works!! Have a great week!! 🎉🎉🎉
Pegasystems Inc.
US
@jassa Found out that additional configuration for 'CommonObjectAuthProfile' is needed. What additional steps do I have to do test on the same Pega Server instance?
Accepted Solution
Updated: 14 Nov 2024 16:20 EST
Pegasystems Inc.
US
@jassa I created a new AdminPCXchg Operator as a replacement in ‘CommonObjectAuthProfile’ profile. Updated password. Added Access Group: PegaHCCore:Administrators to the new Operator. Now works!! Have a great week!! 🎉🎉🎉
