Skip to main content
Feedback

RVR-SSHC-021

  1. Issue Summary:

    • Error Code RVR-SSHC-021 indicates that the key file format for an SSH connection is not in base64 encoding. This commonly occurs when the provided SSH private key is not encoded correctly, which is required for secure data exchanges over SSH connections in Data Integration.

  2. Action Steps:

    • Verify Key File Encoding:
      • Ensure that your SSH key file is correctly encoded in base64. This can be validated by opening the key file in a text editor to confirm that it begins with "-----BEGIN OPENSSH PRIVATE KEY-----" or a similar heading, and ends with "-----END OPENSSH PRIVATE KEY-----".
    • Convert Key to Base64:
      • If the key is not in the correct format, you can convert it using a command-line tool. On Unix-based systems, you can use: 
        openssl base64 -in your_key_file.pem -out your_key_file_base64.pem
      • Replace your_key_file.pem with the path to your original key file, and your_key_file_base64.pem with the desired output file name.
    • Update Data Integration Connection:
      • Access Data Integration and update the SSH connection to use the newly encoded base64 key file.
    • Test Connection:
      • Use the 'Test Connection' feature in Data Integration to ensure everything is set up correctly and verify that the connection is functional.

  3. External References:

    • For more detailed guidance on SSH connections and troubleshooting, refer to Data Integration official documentation: Data Integration Documentation.
    • General information about SSH Key generation and formats can be found in general SSH key documentation.

If the issue persists or you need further assistance, please open a ticket with Data Integration support.