How to Automate Deployment of Keystore Data Instances

In our application, we need a Keystore that is in turn used to generate JWT. When saving the Keystore in development, we uploaded the JKS file and entered the password.

In the Production Environment, the JKS file and password will be provided by the organization's crypto team at the time of deployment.

My question is, how can this be automated? Even if the JKS file is provided ahead of time, how can the Keystore password be saved / referenced automatically without human touch?


Keep up to date on this post and subscribe to comments

August 8, 2019 - 1:30am

You need to enter keystore alias and its password manually in JWT Generation profile. 

August 9, 2019 - 11:08am

The Keystore rule type supports multiple types of keystore instances.  It seems that the two options, data page and URL are the closest to 'automating' this, though it is not real 'automation'.  The 'file' type option might work also.  See the documentation on this on the Pega community site, search for 'Keystores'.  Or try this