How to move Assure Secure File Transfer - 7.0

Assure Security Installation (Manual) Guide
Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure Security > Assure Elevated Authority Manager (EAM)
Assure Security > Assure Encryption
Assure Security > Assure Secure File Transfer
Assure Security > Required for All Modules
Assure Security > Assure Monitoring and Reporting (AMR)
Assure Security > Assure Security Multi-Factor Authentication (MFA)
Assure Security > Assure DB2 Data Monitor (DB2MON)
Assure Security > Assure System Access Manager (SAM)
Assure Security > Assure Secure File Transfer with PGP
Version
7.0
Language
English
Content type
Installation (Manual) Guide
Product name
Assure Security
Title
Assure Security Installation (Manual) Guide
Copyright
2023
First publish date
1999
Last updated
2025-01-05
Published on
2025-01-05T12:58:06.220000
If you use Assure Secure File Transfer, user profiles that initiate SSH sFTP sessions require the user profile’s ~/.ssh directory, typically found in the ‘/home/User/.ssh” directory. Save this directory and restore it to the new system. This will transfer all authorization keys, known host keys, and SSH sFTP password programs used by Assure Secure File Transfer.

If the SSH sFTP user does not exist on the target system, create the profile using the CRTUSRPRF command. This should be done before restoring the save file on the target system in order for the authorities and ownership of the objects to be correct.

Follow these steps:

  1. Create a save file for saving the ~/.ssh directory:
    CRTSAVF FILE(QGPL/SSHUSRSAV)
  2. Save the SSH sFTP user’s ~/.ssh directory, substituting User for the SSH sFTP user profile:
    SAV DEV('/QSYS.LIB/QGPL.LIB/SSHUSRSAV.FILE') OBJ(('/home/User/.ssh/*'))
  3. Move the SSHUSRSAV save file to the target system through the standard method for moving IBM i save files. Create the save file on the target system first and move the save file from the original system into the new save file on the target system.
  4. Restore the ~/.ssh directory, substituting User with the SSH sFTP user profile:
    RST DEV('/QSYS.LIB/QGPL.LIB/SSHUSRSAV.FILE') OBJ(('/home/User/.ssh/*')) CRTPRNDIR(*YES) ALWOBJDIF(*ALL)
  5. Users that migrated from Alliance FTP Manager may have to transfer PGP keyrings to the target system. Alliance FTP Manager used the “/PGP” directory. Users that did not migrate from Alliance FTP Manager do not need to consider the “/PGP” directory as PGP keys will be in the “/VISIONSOLUTIONS” directory that was saved and restored above. If you are using the “/PGP” directory, save the directory:
    CRTSAVF FILE(QGPL/PGPKEYSAV) SAV DEV('/QSYS.LIB/QGPL.LIB/PGPKEYSAV.FILE') OBJ(('/PGP/*'))
  6. Move the PGPKEYSAV save file to the target system through the standard method for moving IBM i save files. Create the save file on the target system first and move the save file from the original system into the new save file on the target system.
  7. Restore the “/PGP” directory:
    RST DEV('/QSYS.LIB/QGPL.LIB/PGPKEYSAV.FILE') OBJ(('/PGP/*')) CRTPRNDIR(*YES) ALWOBJDIF(*ALL)
  8. Optionally, run the following commands to clear log files after restoring the library:
    CLRPFM FILE(SECOPS/ANLOGA)
    CLRPFM FILE(SECOPS/ANHIST)
    CLRPFM FILE(SECOPS/ANLOGP)