I'm creating a digital signature for an integration and I've created a private/public key pair to sign the message. According to the Apex Crypto Class documentation,
This private key should not be hardcoded in the Apex script but should be stored in a protected custom setting or a encrypted fields in a custom table.
but the there's limit for the text fields, and the key obviously surpasses that.
I found a solution that involved splitting the key in and storing it in more than 1 field in the custom setting and then concatenate everything in the code; I don't find this solution extremely good because there are much more chances of something going wrong and consequently messing up the signature.
Does anyone have any other solution/idea?
Thanks in advance.