Posted: 14 Dec 2018 4:47 EST Last activity: 2 Jan 2019 3:26 EST
Default crypto algorithm used in PEGA
There is a requirement to encrypt credentials used in the connector calls from our application as they are stored as clear text in our data tables.
We are currently looking at building our custom cipher as I came across documentation in pdn which did say the OOTB encryption algorithm is not production quality in terms of security. For e.g. if I use encrypt(String) function, what is the default algorithm that would be applied as we don't have a custom cipher and is it correct in us assuming we shouldn't recommend this for production use?
The platform cipher option as I understand can only work with AWS KMS and that in tern can only be used for cloud solutions? Is that correct. Again came across various posts which did mention this but just checking again if that is still true for our version.
What other options have we got in terms of encryption for this requirement? e.g.using a keystore instance to encrypt password stored in our application. Is this possible
I've gone through the above article and whichever ones I came across in the help and community topics w.r.t encryption.
My query still stands -
I see a bunch of engine api methods for this and one of them is encrypt(string). If I use this, the value is encrypted even without the platform or the custom cipher enabled. So, would like some inputs on what is the algorithm used by this function and can it be used for production purposes?