Deployment Manager Configurations when Imported it in the Dev enviornment

Pega-as-a-Service
, , , , , , ,
1

The Post is about the Issues Consolidation and the fixes applied in the environment about Deployment Manager issues occurred when we imported the Deployment Manager in Development Environment itself instead of standard practice to manage the Deployment Manager as a Separate Instance.

Issues and common error is: Deployment Manager will not function as expected when you open the Deployment Manager Portal Post importing it.

  1. HTTP response code 403 error

  2. SSL validation error

  3. Invalid Keylength

DMGR-HTTPS-403.png
DMGR-HTTPS-403.png1150×139 43.2 KB

2

@Kishore Sanagapalli

  1. HTTP response code 403 error

  2. SSL validation error - for Points 1 & 2, Disable the SSL validation during the Service Package / Service connection establishment.

  3. Invalid Key length - Invalid Key length is the issue.

Re-generated the .JKS files with RSA Key Length Size is: 2048 instead of 1024. Issue Fixed.