What to Do When the Decrypt/Encrypt API Fails and/or the Security Screen Is Blank

What to Do When the Decrypt/Encrypt API Fails and/or the Security Screen Is Blank

AuthorFullName__c
David Shin
articleNumber
000005026
ft:sourceType
Salesforce
FirstPublishedDate
2021-03-29T21:42:09Z
lastModifiedDate
2023-01-22T11:05:50Z
VersionNumber
3

This issue can be caused by a user attribute (password, property, etc.) that starts with AM6J or contains spaces. This will interfere with Artifactory’s encryption mechanism. It has been resolved in Artifactory versions 5.8.4 and above. Accordingly, an upgrade will permanently address the problem. Should you encounter this issue in a prior version, the workaround is as follows:

  1. Delete $ART_HOME/data/.deleteForSecurityMarker on the primary node and reboot the node
  2. Run POST /api/system/decrypt
  3. Run POST /api/system/security
  4. Compare the contents of the exported security descriptor to your Source instance and note any
    • non-ascii characters, as these can interfere with the export process
    • usernames, passwords, or properties that start with AM6J
  5. Encrypt the source Artifactory again using POST /api/system/encrypt

If there are no errors, follow these instructions to populate your source:

  1. Rename security.xml to security.import.xml
  2. Decrypt Artifactory using POST /api/system/decrypt
  3. Move security.import.xml to the $ART_HOME/etc directory
  4. Restart the target node
Encrypt the target using POST /api/system/encrypt

Published: Jan. 21, 2019

Last updated: Mar. 15, 2021

Keywords: decrypt API, encrypt API, blank security screen