Question: How to keep OpenAM up to date/patched without human intervention

Tagged: , ,

This topic contains 1 reply, has 1 voice, and was last updated by  dhartford 3 months ago.

  • Author
  • #19981

    Hi Everyone,
    Is there a supported process/approach to, either through Ansible or via Docker images, to keep an OpenAM instance up to date *without* requiring Human Intervention? (under the context of CI/CD where automated testing will occur on the patched/updated version)

    Currently, it seems the only way to get updated versions is to manually log into the update site to get the zip files with credentials…looking for solutions to automatically get updated (supported/paid-for) versions of OpenAM without relying on human intervention.

    Historical and current solutions for other platforms include Maven repositories and Docker registries that you can setup API/Service Accounts with for automation, but I don’t see anything like that for Forgerock/OpenAM, hopefully I’m just missing something, please assist :-)


    • This topic was modified 3 months, 2 weeks ago by  dhartford.

    Just checking in…for example, if you use the devops instructions from here:

    There is this statement because it still requires human intervention:

    The Dockerfile assumes that the openam.war file is pre-downloaded in this directory.

    How can we automate that process, such as from a credentialed maven repository with a service account?

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

©2018 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?