Importing Identity Server configuration data includes the following steps:
In the Import Identity Server Clusters section, specify the import action for each cluster available in the imported configuration. Select the desired options based on your requirements.
NOTE:Importing Identity Server configuration overwrites the existing Shared Settings on the system with the new Shared Settings. However, if any of the existing settings on the target system are not part of the source system configuration, Code Promotion does not delete them.
The following table lists examples with Attribute Sets and import action:
|
Imported Attribute Sets |
Existing Attribute Sets |
Import Action |
|---|---|---|
|
OIOSAML with five mappings |
OIOSAML with two mappings |
Replaces OIOSAML set with the imported one. It has five mappings. |
|
AttrSet1 |
Not available |
Adds AttrSet1. |
|
No import |
AttrSet2 is defined only in the target system |
AttrSet2 remains unchanged. |
In Clusters To Import, select a cluster to configure import settings.
Select an action for the selected cluster from Import Action.
Import As New Cluster: Select this option if you want to import the cluster as a new cluster. Ensure that the new cluster name is different from the existing cluster names defined on that system.
Overwrite Existing Cluster: Select this option if you want to overwrite the existing cluster with the selected cluster.
NOTE:You need to configure the import action for each cluster separately. If the cluster you want to import has only one user store, Code Promotion maps the user store to the default user store of the existing cluster. If the cluster you are importing has multiple user stores, then you must specify how to map them to the user stores of the existing cluster.
Click Next.
Continue with Section 31.6.5, Post-Import Configuration Tasks.