Value Processors for CONGA
Description
Gliffy Diagrams
Activity
Stefan Seifert January 8, 2018 at 5:16 PM
for the last usecase i've added a new handlebars helper "aemCryptoEncrypt" which support encrypting passwords or other secrets using AEM crypto key (which has to be deployed to AEM as well).
http://devops.wcm.io/conga/plugins/aem/handlebars-helpers.html
Stefan Seifert January 4, 2018 at 5:26 PM
after thinking about the requirements i found a good solution for the 2nd and 3rd usecase example:
build a password hash for a oak user based on his password
build a UUID for a oak user based on it's principal
i've implemented handlebar extensions for these in the AEM CONGA plugin - oakPasswordHash and oakAuthorizableUuid
http://devops.wcm.io/conga/plugins/aem/handlebars-helpers.html
leaving this ticket open for the last use case
encrypt a publisher password using AEM Granite Crypto Support for storage in JCR
Details
Details
Assignee
Reporter
Stefan SeifertComponents
Priority
Major
currently all conga config parameters are placed 1:1 in the generated target files (or perhaps escaped with escaping rules required for the target files).
there are use cases where we need to process the value before placing it in the target file, e.g.:
encrypt a publisher password using AEM Granite Crypto Support for storage in JCR
build a password hash for a oak user based on his password
build a UUID for a oak user based on it's principal (if there is really such a dependency)
the processing could be executed in the handlebars templates using a specific handlebars expression.
it should be possible to pass in optional parameters to the value processor, e.g. the hasing alogrithm to be used.