To copy a client app's configuration from a source tenant to a destination tenant, export the app's configuration from the source tenant, and then import it into the destination tenant. You can export and then import one or more configured apps, and you can optionally include any of the app's dependencies.
Exporting
Using the Admin Console
Login to the Admin Console and, if needed, switch to the source tenant. This is the tenant that already has the app configured. Navigate to Configuration > Apps.
The Apps page appears.
To export all apps, click Export All.
To export a specific app, locate the app in the table and, in the same row, click the Export icon in the Actions column.
The Export App dialog appears.
If you assign a default Adaptive Ruleset to an app, that Adaptive Ruleset has dependencies that need to be exported. Those dependencies include FIDO policies, authenticator groups, country lists, device model lists, geofence lists, IP address lists, and WiFi network lists. Check With dependencies to export these objects.
You can optionally Include authenticator metadata to export authenticator metadata. This option is only valid if you checked With dependencies. Use this option in limited situations, such as when you intend to use authenticator metadata that was only in a development deployment in a production deployment. Remember, authenticator metadata is accessible to all tenants in an S3 installation. Normally, you should use the instructions in Update Authenticator Metadata to import metadata.
Click Export.
If you are exporting one or more apps without dependencies or authenticator metadata, the Admin Console saves the app(s) in a JSON file.
If you are exporting app(s) with their dependencies, the Admin Console saves all the objects in a ZIP file.
Using nnl-mgmt.sh
The syntax below shows how to export the configuration for the app with <package-name> from <tenantid> into a file. If no <tenantid> is specified, the app is exported from the default tenant. The <app-dir> or <file-path> specifies where the system stores the app's configuration.
./nnl-mgmt.sh app export -name <package-name> [-dir <app-dir> | -file <file-path>] [-with-dependencies <yes|no> -include-metadata <yes|no> -tenantid <tenantid>]For more information, see App Commands in the reference to Command Line Interface.
Importing
Using the Admin Console
Login to the Admin Console and, if needed, switch to tenant2. This is the tenant into which you want to import the app configurations. Navigate to Configuration > Apps.
On the Apps page, click the Import… button.
The Import Apps dialog appears.
To overwrite apps in the current tenant that have the same package name, check Overwrite any existing app with the same package name. Note that if your zip file contains dependent objects, this option also overwrites any dependent objects with the same name.
Check Import and overwrite metadata as well from zip file to import authenticator metadata from zip file. Use this option in limited situations, such as when you intend to use authenticator metadata that was only in a development deployment in a production deployment. Authenticator metadata is accessible to all tenants in an S3 installation. Normally, you should use the instructions in Update Authenticator Metadata to import metadata.Choose the json or zip file that contains the app configuration and click Import. By default the file size can be up to 512 KB. To change the maximum file size for an app configuration file, refer to Admin Tenant Properties.
Using nnl-mgmt.sh
The syntax below shows how to import an app's configuration file into <tenantid>. If no <tenantid> is specified, the default tenant is used.
./nnl-mgmt.sh import -file <property-file> [-overwrite <yes|no> -include-metadata <yes|no> -tenantid <tenantid>]For more information, refer to App Commands.