Hide Forgot
Description of problem: standalone/configuration/dtgov.properties:sramp.repo.password=password1# standalone/configuration/dtgov.properties:governance.bpm.password=password1# standalone/configuration/dtgov.properties:governance.password=password1# Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I believe this will be resolved post-beta with the use of the vault.
All of the overlord apps now support using vaulted passwords in their config files rather than plain text. In this particular case the installer needs to be updated to do the following: 1) create/init the EAP vault 2) auto-generate a password for a dtgov service user named "dtgovworkflow" 3) create the dtgovworkflow user via 'add-user.sh' or equiv. 4) store the generated password in the EAP vault 5) write the dtgovworkflow username and generated password's vault key to dtgov.properties (instead of using the plain text password entered by the user) Further details of this have been documented elsewhere for reference by interested parties. Assigning this BZ to thauser to complete the prod installer changes.
Changes for this should be complete for ER7. Need the full build for confirmation.
Verified in ER7-2 grep password dtgov.properties sramp.repo.password=${vault:VAULT::dtgov::dtgov-workflows.password::1} governance.bpm.password=${vault:VAULT::dtgov::dtgov-workflows.password::1} governance.password=${vault:VAULT::dtgov::dtgov-workflows.password::1}