Configure policy and application stores
Setting up an external policy or application store involves the following steps:
Configuring the connection between AM and the directory server.
Enabling a realm to use the newly configured directory server.
These steps assume you have installed and configured DS as a policy or application store.
In the AM admin UI, go to Configure > Global Services > External Data Stores.
On the Secondary Configurations tab, click Add a Secondary Configuration.
Complete the form as follows:
In the Name field, enter a name for the data store; for example,
If you’re ready to use this data store, select Enabled.
If you enable an external data store configuration, AM checks that it can connect to the server when you save the configuration.
You can’t select a data store configuration for use (at the realm or global level) until you enable it.
If you’re configuring mTLS authentication to the data store, don’t enable the connection until you have added an mTLS Secret Label and the corresponding entry in the secret store. You can’t do this on the create page. You must save the configuration, then edit it to add the mTLS Secret Label.
In the Host Urls field, enter one or more connection strings. The format for each connection string is
HOST:PORT; for example
AM uses the first connection string in the list unless the server is unreachable. In this case, it tries the next connection strings in the order in which they’re defined.
Enter the Bind DN and Bind Password of the service account AM uses to authenticate to the data store.
Select Use SSL to connect to the directory server over SSL.
Select mTLS Enabled to authenticate to the directory server using mTLS instead of a bind DN and password.
If you enable mTLS, you must also:
AM ignores the values of the Bind DN and Bind Password when mTLS Enabled is
Specify whether the directory servers you’re using as application and policy stores use affinity load balancing, rather than a single primary directory instance in an active/passive deployment.
If you enable this option, specify each of the directory server instances that form the affinity deployment in the Host Urls field.
To save your changes, click Create.
If the configuration is Enabled, AM attempts to connect to the data store using the specified settings, saves the connection, and makes it available for use as a policy or application store.
If the connection is unsuccessful, AM logs an error:
Failed to load resource: the server responded with a status of 400 ().
On successful connection, AM attempts to change the schema and structure of the external directory server. If the specified Bind DN property doesn’t have permission to change the schema and structure, you must apply the required settings manually. For details, refer to Prepare external stores.
You can select an external data store for use at the global or realm level only when it’s Enabled.
To edit the connection settings:
Click the Secondary Configuration tab and click the name of the data store configuration.
Add an mTLS Secret Label.
AM uses this label to create a specific secret ID for this policy or application store. It uses the secret ID to map to the mTLS certificate in the secret store.
The generated secret ID takes the form
labelis the value of mTLS Secret Label. You can only view and map the secret ID after you have set the label.
The label can only contain alphanumeric characters (
0-9) and periods (
.). It can’t start or end with a period.
All LDAP servers configured for this policy or application store share the same secret label.
Click Save Changes.
Repeat these steps for additional policy or application stores.
|Changing the policy or application store will cause any existing policies or applications to become unavailable to the realm.|
Either recreate the policies or applications manually, or use Amster to export the existing instances, then import them back after changing the stores.
In the AM admin UI, go to Realms > Realm name Services.
Configure the External Data Stores service in the realm:
If the External Data Stores service has not yet been added to the realm, click Add a Service, and select External Data Stores.
If the External Data Stores service has already been added to the realm, click External Data Stores to edit the configuration.
On the External Data Stores page, select the name of the store to use as the Policy Data Store and/or Application Data Store, and click Save Changes.
If you choose the
Default Datastoreoption for either property, AM will use the configuration data store that was specified during installation.
Changes take effect immediately. New policies or applications are created in the configured data store.
Follow these steps to remove a policy or application store from a realm, and to delete the store from the AM configuration.
|You can’t remove a policy or application store a realm is currently using.|
For each realm that’s using the store, in the AM admin UI, go to Realms > Realm Name > Services > External Data Stores, and change each of the drop-down menus to either
Default Datastore, or an alternative data store.
Save your changes.
Go to Configure > Global Services > External Data Stores > Secondary Configurations. Click the name of the store to remove, and click the delete icon.
If the data store is still in use, AM returns the following error message:
Unable to modify data store instance because it is referenced by the data store service of realm /Realm Name
In this case, repeat the first step to remove the unwanted store from the listed realm, then repeat this step.