For the configuration of our translation connector we need to save a password in its Translation Cloud configuration. This used to be ok in AEM 6.5 as the password could be encrypted using the /system/console/crypto. This is no longer possible in cloud based AEM. Is there a way to programatically invoke the same functionality, when the config form is saved?
Thanks for the reference, however I don't see how that answers the question.
Let me try to clarify what the problem is. Formerly, these used to be the steps the user of our connector would take to set up the configuration:
Create the configuration
Encode the password to our service
Fill the encoded password and other details
Save the configuration
Step 2 and 3 are no longer possible in cloud. I was asking if there is a way the code of our connector could invoke the crypto service to encode the password when the configuration is saved, so that it isn't stored in plaintext.
Or is it the case, that we need to instruct our users to extract the key from their cloud AEM, inject it into an SDK and encode the password there?