With standard encryption, accounts are encrypted with cloud-managed keys. With 85131302, accounts are encrypted with public/private keys that you manage through a Groundplex on your local network.

When you Migrate accounts from one org to another orgOrganizations with multiple Orgs can migrate Accounts from one Org to another. There are several ways to migrate Accounts:

• From the Project options menu:
  • Export to a zip file and import to the target Org.
  • Migrate from one Org to the other.
• From the Assets table: 
  • Select the Accounts to migrate and click the toolbar Copy button.

Both Project options allow you to migrate all accounts. To migrate individual Accounts, select them in the Assets table and copy them.

Encryption for Migrated Accounts

It is possible for different Orgs owned by the same organization to use different types of Account encryption. Because of the security risk, SnapLogic does not support the migration of accounts from Orgs with Enhanced Encryption to Orgs using standard account encryption. In this situation, you must manually recreate the accounts in the target Org.

When you Migrate Accounts from one Org to another, consider the following:

• The new accounts you create with import/migrate/metadata Accounts you create by importing or migrating a Project or by copying from the Assets table are automatically re-encrypted with destination org Org keys when you migrate the account from one orgOrg (source org) to another Org (destination), provided:
• You are migrating the accounts from an org Org with standard account encryption to an org Org with standard or enhanced account encryptionEnhanced Encryption. In this case, the source org is required to Org must be configured to recognize the destination org Org as a trusted orgOrg. Org admins can configure Organizational Organizational Settings to  to establish trust between orgsOrgs. 
• You are migrating the accounts from an org with enhanced account encryption to another org with enhanced account encryptionOrg with Enhanced Encryption to another Org using Enhanced Encryption. In this case, the customers are required to you or a Snaplex administrator must add the source org’s Org’s private keys to the JCC keystores in the destination orgOrg. The source private keys should be added with an alias name different from that of the destination key alias for alias names are unique  in the keystore. A recommended name for source key alias will have org name preceded to the default ‘account-autogen’ key alias.
• Because of the security risk, SnapLogic does not support migration of accounts from orgs with enhanced account encryption to orgs with standard account encryption. In this situation, you must manually recreate the accounts in the target org.
• Projects with accounts exported prior to Release 4.11 will not have the accounts re-encrypted on import. You need to export the projects again and import in the target org. 
• . We recommend that you append the Org name to the source key alias.

• If your org is configured for Enhanced Account Encryption, the SnapLogic Create Snap and the SnapLogic Update Snap enable you to create/update accounts when the sensitive fields are provided in plain text. The Snaps will encrypt the data automatically.
  

  Note
  The presence of 'key' in the property tells the Snap that the field is already encrypted. Therefore, when the property value is in plain text, make sure you delete the 'key' field in the sensitive property object. Otherwise, the Snap cannot encrypt the field.

  
  

Migrating from One Enhanced Encrypted Org to Another

...

keytool -importkeystore -srckeystore jcc-datakeys.jks
-srcstoretype JCEKS -srcstorepass `cat jcc-datakeys.pass` 
-srcalias 'account-autogen' -destkeystore <destination-machine>:<keystore-location>/jcc-datakeys.jks -deststoretype JCEKS 
-deststorepass <destination-machine>:<keystore-location>/jccdatakeys.pass -destalias source-account-autogen 

1. Export the source key to a temporary keystore. 

   Code Block
   keytool -importkeystore -srckeystore  jcc-datakeys.jks -destkeystore  jcc-datakeys-src-copy.jks -srcstoretype JCEKS -deststoretype JCEKS -srcstorepass  `cat jcc-datakeys.pass` -deststorepass changeit -srcalias account-autogen -destalias source-account-autogen -srckeypass  `cat jcc-datakeys.pass` -destkeypass changeit

   
   

   Note

   Both source and destination key-aliases are by default account-autogen. So while importing the source key to destination, a new name should be chosen for source key-alias. A recommended name would have source org name followed by account-autogen. For example, SnaplogicDev-account-autogen. The keys are accessed by the same password that is used for the store that is stored in a .pass file. While exporting the source key to a temporary keyfile, use a temporary password. For example, changeit.

...

1. 
   

2. Copy the temporary keystore to the destination JCCs.

...

1. Go to the keystore in the destination JCCs. Import (add) the source key to the destination key using the following command:

   Code Block
   keytool -importkeystore -srckeystore  jcc-datakeys-src-copy.jks  -destkeystore jcc-datakeys.jks -srcstoretype JCEKS -deststoretype JCEKS -srcstorepass changeit -srckeypass changeit -deststorepass `cat jcc-datakeys.pass`  -srcalias source-account-autogen  -destalias source-account-autogen

...

1. 
   

2. Change the source key password to use the keystore password.

   Code Block
   keytool -keypasswd -alias  source-account-autogen -keypass changeit  -new `cat jcc-datakeys.pass`

...

1. 
   

2. Once the keys are added, you can list the keys to confirm that the source key is added with alias source-account-autogen


   Code Block
   keytool -list -keystore jcc-datakeys.jks  -storetype JCEKS -storepass `cat jcc-datakeys.pass`