Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle custom AEM passwords #41

Closed
krystian-panek-vmltech opened this issue Jan 17, 2023 · 2 comments · Fixed by #43
Closed

Handle custom AEM passwords #41

krystian-panek-vmltech opened this issue Jan 17, 2023 · 2 comments · Fixed by #43
Labels
improvement Improvement to an existing feature
Milestone

Comments

@krystian-panek-vmltech
Copy link
Contributor

checker should be aware of admin:admin pair being active before reaching initial 30% of stable bundles (AEM auth is initialised at this stage)

@krystian-panek-vmltech krystian-panek-vmltech added this to the 1.0.0 milestone Jan 17, 2023
@krystian-panek-vmltech krystian-panek-vmltech added the improvement Improvement to an existing feature label Jan 17, 2023
@krystian-panek-vmltech
Copy link
Contributor Author

krystian-panek-vmltech commented Jan 23, 2023

introduce aem user update-password --id admin --password <pwd>
if id == admin then AEMC will store internally password encrypted by salt

base:
  security:
    algorithm: AES256
    salt: <RANDOMLY_GENERATED_UPON_CONFIG_INIT>

or that salt could be set on nodes as environment variable .Env.AEM_BASE_SALT

security constraints assumed:

  • when called from aemc-ansible, the file aem.yml with that salt will be only temporarily persisted on VM; Ansible ensures to clean that file immediately after module execution
  • that file will be created with read-only permissions for root user (Ansible user who is executing the module); no-one else will be able to read that value

AEMC should be able to rotate admin password when used to check its stability as:

  • AEM on first run before reaching 30% of bundles stable is using default admin pwd instead of the target one - e.g set by -Dadmin.passwordfile= so that during single AEMC command the 2 different passwords need to be used and such case need to be supported

@krystian-panek-vmltech
Copy link
Contributor Author

implemented previous-password-less approach using oakrun;

image

only to be polished / that jansi error especially - https://issues.apache.org/jira/browse/OAK-5961

@tomasz-sobczyk-wttech WDYT?

I decided to embed oak-run to aemc binary to avoid unexpected file downloads occurrence when oak-run will be needed on password change; 50mb; what is interesting only 1.42 version works, newer ones are broken (corrupted jar file / not launchable, too small size)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement to an existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant