New Configuration Model¶

Configuring MWARE IAM is made easier with a simplified, centralized configuration model that supports injecting configurations with multiple methods such as environment variables, to improve compatibility with different configuration automation tools and cloud native environments. The following sections compare the previous configuration model and new configuration model.

Previous configuration model¶

MWARE IAM is built using a collection of components out of which many had their own configuration files such as carbon.xml, identity.xml, and axis2.xml. This configuration model had several drawbacks:

• Flawed user experience:
  • The users had to focus on component-level configurations instead of product-level configurations, and the basis of the component-level configurations was not clearly evident to the user.
  • Enabling a single functionality may require changing multiple configuration files that could result in a lot of human errors.
• Lack of structure in the configuration files
• Inconsistent parameter nomenclature
• Varied time units used in different configuration files
• Optional configurations were also visible to the user.

New configuration model¶

With the new configuration model from MWARE IAM 5.9.0 onwards, configurations are handled by the deployment.toml file in the <IS_HOME>/repository/conf/ directory. The benefits of this new configuration model include:

• Without being concerned about the components, the users can focus on the configurations.
• Minimal chance for human errors during configuration
• The users will only see the mandatory configurations where certain mandatory configurations shall be inferred without human intervention.
• Ability to use a proper time unit for a configuration
• Configurations are well-grouped and consistently named