Question
Department of Human Services, Australian Government
AU
Last activity: 30 Jan 2023 8:41 EST
Pega Deployment Manager 5.4 gives exception Access Token Not Found
We have installed the Deployment Manager 5.4 on Pega Infinity 8.5.2 platform as per the installation guide and followed every instruction properly but unfortunately, upon launching the Deployment Manager, we are getting the following :
There is an error fetching details from Deployment Manager services <Pega URL> and Deployment Manager Studio will not function as expected. Please verify the configuration of the Orchestrator URL and authentication profiles configured. Error: Access token is not found will not function as expected. Please verify the configuration of the Orchestrator URL and authentication profiles configured.
Error: Access token is not found
The log indicates as below:
2021-12-15 15:53:44,060 [ STANDARD] [ ] [aDeploymentManager:5] (ernal.jwt.JWTSignatureVerifier) ERROR |Rest|DeploymentManager|v1|- JSON web token is rejected during signature verification due to bad signature : Expired JWT 2021-12-15 15:53:44,060 [ STANDARD] [ ] [aDeploymentManager:5] (uth2JWTTokenProcessingUtilImpl) ERROR Rest|DeploymentManager|v1| - Error while processing JWT JSON web token is rejected during signature verification due to bad signature : Expired JWT
We have checked and verified everything we could find after checking other articles on the Pega collaboration site but the issue is still unresolved.
We would appreciate help to resolve this issue.
Accepted Solution
Updated: 19 Jan 2022 10:46 EST
Department of Human Services, Australian Government
AU
@TapasD07 This issue was happening due to DMStudioUser authentication profile has incorrect setting under advanced configuration - 'Send access token as Query string parameter'.
Changing this setting to 'Authorization header' resolved the issue.
Forvandle
IN
@TapasD07 Hi Tapas,
We also facing same issue,
We have checked DMStudioUser setting as well and for us it is selected Authorization Header only. We are still facing this issue.
Department of Human Services, Australian Government
AU
@Priyanshu Please ensure you are using Deployment Manager 5.5 or even better try the latest :)
IKOR PX
GB
@TapasD07 - any resolution you got?
We are using PDM 5.5.4 with Orchestrator on Pega 8.5.6 and Candidate on Pega 8.5.1> getting similar error:
2022-12-19 13:41:59,033 [fault (self-tuning)'] [ STANDARD] [ ] [aDeploymentManager:5] (ernal.jwt.JWTSignatureVerifier) ERROR ||Rest|DeploymentManager|v1|tasks2cb1ad4f3eb0ea704c74a73689ad1654|A3KQ5YAAV6FGAKEW8I6VAH35IE9YB7TEKA - JSON web token is rejected during signature verification due to bad signature : Expired JWT 2022-12-19 13:41:59,033 [fault (self-tuning)'] [ STANDARD] [ ] [aDeploymentManager:5] (uth2JWTTokenProcessingUtilImpl) ERROR ||Rest|DeploymentManager|v1|tasks2cb1ad4f3eb0ea704c74a73689ad1654|A3KQ5YAAV6FGAKEW8I6VAH35IE9YB7TEKA - Error while processing JWT JSON web token is rejected during signature verification due to bad signature : Expired JWT 2022-12-19 13:41:59,033 [fault (self-tuning)'] [ STANDARD] [ ] [aDeploymentManager:5] (th2.cxf.OAuth2DataProviderImpl) ERROR ||Rest|DeploymentManager|v1|tasks2cb1ad4f3eb0ea704c74a73689ad1654|A3KQ5YAAV6FGAKEW8I6VAH35IE9YB7TEKA - Error in Processing JWT DMStudioUser authentication profile has Authorization header.
Thanks
Atanu
IKOR PX
GB
My issue is resolved.
Set this DSS on both candidate and orchestrator:
DSS : https/allowAllHostnames Ruleset : Pega-IntegrationEngine value : true
Messages in log file bit misleading. :)
Tata Consultancy Services
US
@TapasD07 Do we have any other solution to fix this issue? We have done everything mentioned in this thread and Pega Documentation but still getting same error.
Dictu
NL
@folks, we are running our orchastrator on pega 8.6.6 ( with deployment manager 5.5.4 v and candidate env 8.7.4. Few months back when we were upgrading our orchastrator env from 4.x to 5.5.x we faced this kind of issue.(New tab (pega.com))
we also added few DSS those are mentioned on the above pega link and after setting up everything and restart, we were able to do merge and deployment.
Hope this will help here.. Good luck
| Sr no | Env | Opertor ID | Auth Profile | Details |
|---|---|---|---|---|
| 1 | Orchastrator |
|
DMAppAdmin |
Please change the password of these operatorID's and Auth profile with the unique password and keep it synchronised on all the environments like Orchastrator & candidate system (DEV,TEST). i,e Password for DMAppAdmin should be same on Orchastrator env and Candidate system (DEV and TEST) |
| 2 | Candidate | DMAppAdmin |
DMReleaseAdmin_OAuth2 |
You can generate new client secret code from orchastrater general setting and then use this code and respectivce url's to update on candidate env. |