Amster and the AM config-store in a site

This topic has 15 replies, 4 voices, and was last updated 4 years, 3 months ago by Warren Strange.

  • Author
  • #21107
     Warren Strange

    The “cloning” procedure mentioned above is oriented at an environment where all AM nodes have exactly the same configuration (cattle – not pets). A single install is done, and each AM node points at the same configuration store. There are restrictions with that model noted above (see notes on sticky load balancing, etc.)

    If you want to have two different AM configurations (primary / secondary) you should be able to script that using amster. You will have two different amster imports, or one import, and apply some kind of search/replace on the elements that you want to customize for each install.

    Tl;DR – Everything that your ssoadm script does you should be able to replicate using amster.

Viewing 16 post (of 16 total)

You must be logged in to reply to this topic.

©2022 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?