Delinea / Thycotic Secret Server Import

Automatic migration of your Delinea (Thycotic) Secret Server vault

Secret Server Import

This document outlines the process for automatically and seamlessly migrating Secret Server (Delinea/Thycotic) data into Keeper which includes private folders, shared folders, permissions, file attachments, TOTP codes. This process utilizes the Secret Server API to automate the process.

Note: A basic import capability is available on the Keeper Web Vault and Desktop App which supports Thycotic XML format. Visit the vault Settings > Import > Thycotic screen. The XML format does not include attachments or permissions. Therefore, we recommend using the automated method as described in this document.

Make sure Webservices are enabled

In Secret Server admin settings, ensure Webservices are enabled

Admin -> Configuration -> Edit -> Enable Webservices

Secret Server Configuration

In Secret Server admin settings, ensure that "Session Timeout for Webservices" is set to a high enough value, since large vaults will take time to process. For example, 59 minutes.

Session Timeout

Step 1. Download Team and Shared Folder Structure

In Keeper Commander, the Keeper/Thycotic Administrator will run the following:

download-membership --source=thycotic
...     Thycotic Host or URL: https://xyz.acme.com/secretserver
...     Thycotic Username: acme.com\user

Prior to running the above code snippet, make sure to:

• Verify the base Thycotic URL in your browser

• The Username is in the correct format:

  • If it's a AD user, the format is DOMAIN\username otherwise username

Executing the above code snippet will perform the following 3 functions:

• Download all Shared Folder information

• Download Team Membership

• Download Shared Folder permissions

This step downloads a file locally called "shared_folder_membership.json" which contains the team and shared folder structure.

Keeper does not yet support folders within shared folders that have different permissions than the parent.

download-membership command provides an option --sub-folder to control how these folders are imported.

--sub-folder=ignore preserves folder structure. Folder permissions are ignored.

--sub-folder=flatten folder will be moved to the root folder of the Keeper vault as its own shared folder.

Step 2. Import Shared Folders

Before importing records, we will first create the shared folder structure on the Keeper side. Run the below command:

import --format=json shared_folder_membership.json

Step 3. Export TOTP Codes

The TOTP codes stored in Thycotic/Delinea Secret Server can only be retrieved by manually downloading a CSV file. The admin of Secret Server needs to go to Secret Server > Export Secrets and select the following options:

• Export Type: Export All

• Export Folder Path: Checked

• Export TOTP Settings: Checked

• Export Format: CSV

Export the file and save it to your home folder, or the folder where Keeper Commander is running. The file will be called "secrets-export.csv" by default.

Step 4. Import the Secret Server Vault

In Keeper Commander, the Keeper/Thycotic Administrator will run the following command to perform the import of data using the Secret Server API:

import --format=thycotic https://your-secret-server-hostname
or
import --format=thycotic username@your-secret-server-hostname

This command will take several minutes (or more) to complete, depending on the number of vault records and users. A large Secret Server instance could take 20 minutes or more.

Commander will attempt to build the same folder structure as Secret Server in the admin's Keeper vault.

Commander will also look for the file "secrets-export.csv" in the user's home folder or current Commander folder, for the purpose of importing TOTP codes.

Note 1: This command will import and populate regular folders, shared folders and records within the folders. This will NOT import the private folders of other users within Secret Server. This step will only import the information available to the admin.

Note 2: If a Shared Folder is found within another shared folder with different permission, the shared folder will be moved to the root folder (since Keeper does not support subfolder permissions).

Step 5. Apply Membership Permissions

In Keeper Commander, the Keeper/Thycotic Administrator will run the following:

apply-membership

This will read the file called "shared_folder_membership.json" from Step 1 and apply the shared folder permissions for any users and team which exist in the Keeper enterprise environment. This command is safe to run over and over again, and it will not generate duplicates.

Explanation: When users are invited/created through SSO or your invitation process, their public keys are created. Therefore, Keeper cannot apply membership until the users exist.

For this reason, the Keeper Admin needs to run the "apply-membership" command on a daily basis, hourly, or on demand, when users are created in Keeper.

Step 6. End-Users are invited to Keeper

The Keeper Admin will invite users through one of the following methods:

• Just-in-time provisioning through SSO login

• Invite through the Admin Console

• SCIM

When the user registers to create their vault, they will generate a public/private key pair. At this point, they will be able to receive shared folders, as outlined in the next step.

Receiving Shared Folders

The next time that the Admin runs the apply-membership command, any new Keeper users will receive access to their Shared Folders.

Due to the number of steps, we recommend performing a pilot test with a few users before rolling out to the entire organization.

If you have any questions please email [e-mail].