

Deployment Checklist¶

Guideline	Details
Security hardening	Guidelines for hardening the security of a MWARE IAM deployment in a production environment can be discussed under three high-level categories: Product-level security OS-level security Network-level security Related topics Security Guidelines for Production Deployment
Hostname	By default, MWARE IAM identifies the hostname of the current machine through the Java API. However, this value sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname by setting the relavent parameter in the `<IS_HOME>/repository/conf/deployment.toml` file. Related topics Change the hostname
Userstores	MWARE IAM offers three choices to store user details: Using a database Using an LDAP server Using an Active Directory service The default is the embedded H2 database, with the userstore schema. Like in the case of the registry database, you can switch to a database like Oracle, MySQL, or MSSQL. You can point to an existing LDAP or an Active Directory to make use of existing user bases and grant access privileges based on those userstores. Related topics Working with Databases
Tuning WSO2 products	MWARE IAM has additional guidelines for optimizing the performance of product-specific features. Related topics Performance Tuning Recommendations
Firewalls	The following ports must be accessed when operating within a firewall. 9443 - Used by the management console and services that use the servlet transport, and is defined in the `<IS_HOME>/repository/conf/deployment.toml` file. Related topics Default Ports of MWARE IAM
Proxy servers	If the product is hosted behind a proxy such as ApacheHTTPD, users can configure products to use the proxy server by providing the following system properties at the start-up. `-Dhttp.proxyHost=xxxx -Dhttp.proxyPort=xxxx` Alternatively, this can be done by adding the following configurations in the `< IS_HOME>/repository/conf/deployment.toml` file. `[transport.https.properties] proxyhost : "you.proxy.host" proxyPort : "your.proxy.port"`
High availability	For high availability, MWARE IAM must run on a cluster. Databases used for the repository, user management, and business activity monitoring can also be configured in a cluster or can use replication management provided by the RDBMS.
Data backup and archiving	For data backup and for archiving of data, use the functionality provided by the RDBMS.

Top