Saving password inTranslation Cloud config

Avatar

Avatar

JanHumpal

Avatar

JanHumpal

JanHumpal

17-03-2021

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?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

JanHumpal

Avatar

JanHumpal

JanHumpal

22-03-2021

Hello Arun!

 

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:

  1. Create the configuration
  2. Open /system/console/crypto
  3. Encode the password to our service
  4. Fill the encoded password and other details
  5. 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?

Answers (1)

Answers (1)

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

3.1K

Likes

1.2K

Correct Reply

883

Avatar

Arun_Patidar

MVP

Total Posts

3.1K

Likes

1.2K

Correct Reply

883
Arun_Patidar
MVP

18-03-2021

Please check https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem...

 

 

In case you depend on CryptoSupport (either by configuring the credentials of Cloudservices or the SMTP Mail service in AEM or by using C...), the encrypted properties will be encrypted by a key that is autogenerated on the first start of an AEM environment. While the cloudsetup takes care of automatically reusing the environment-specific CryptoKey, it is necessary to inject the cryptokey into the local development environment.