QuestionQ25

VerifiedAdobe Experience Manager Sites Architect Master

A website hosted on AEM as a Cloud Service (AEMaaCS) uses a private key to decrypt data received from a secure web platform. The private key is stored as an encrypted OSGi configuration on the AEM publishers by using the OOTB AEM Crypto Support bundle. Developers report that, although the feature works in the AEMaaCS environments, they cannot decrypt the data in the local development environment.

Which two actions should the architect take to resolve the issue?

Choose two
Explanation

CryptoSupport encryption is bound to an instance-specific master key, so a value protected in an AEMaaCS environment cannot be decrypted by a local SDK instance with a different key. Initializing local AEM with -Dcom.adobe.granite.crypto.file.disable=true stores its crypto key data under /etc/key, supporting reusable local development. The private-key value must be obtained in clear text through CryptoSupport in the originating environment and protected again using the local instance’s Crypto Support console, thereby binding it to the local key.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!