Code Promotion uses names to associate entities from the source system to the target system. It searches on the source system for names that are part of the import. If it finds Access Gateway entities with the same names, it overwrites these entities. If not available, it creates new entries with the same names from the source system. When Identity Server and policies-specific entities with the same names are available, you can select whether to overwrite these.
If the policy name, policy extension, and proxy service match on the source and target systems, but their type does not match, the import does not happen.
Code Promotion does not export Access Gateway clusters, reverse proxies, and master proxies. Before importing Access Gateway configuration data, you must manually create clusters, reverse proxies, and master or root proxy services in the target system.
If you want to import Access Gateway protected resources that require Identity Server configuration other than contracts and its dependencies, LDAP attributes, and Shared Secret, first import the required Identity Server configuration. For example, for risk-based authentication or OAuth configuration, import the relevant Identity Server configuration separately. You can import these configurations manually or by using Identity Server Code Promotion.
NOTE:If the reverse proxy in the source system is non-HTTP and in the target system is HTTPS or vice-versa, ensure that you have tested the configuration before importing. In this case, the import might result in issues if there is any issue in the browser to Access Gateway communication.
Importing Access Gateway configuration data includes the following steps: