Guidelines for hardening the security of a WSO2 Identity Server deployment in a production environment can be discussed under three high-level categories:
By default, WSO2 Identity Server 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
WSO2 Identity Server offers three choices to store user details:
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.
|Tuning WSO2 products
WSO2 Identity Server has additional guidelines for optimizing the performance of product-specific features.
The following ports must be accessed when operating within a firewall.
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.
Alternatively, this can be done by adding the following configurations in the
For high availability, WSO2 Identity Server 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.