Payables & Cash Management

Get Involved. Join the Conversation.

Topic

    Ryan Tilles
    Export an Oracle-generated SSH private key?Answered
    Topic posted May 22, 2019 by Ryan TillesRed Ribbon: 250+ Points, tagged Configuration, Financials, Payables, Setup / Administration 
    79 Views, 8 Comments
    Title:
    Export an Oracle-generated SSH private key?
    Summary:
    Export an Oracle-generated SSH private key?
    Content:

    If we used Oracle's "create" tool to generate an SSH key pair (within the Transmission Configuration page), is it possible to later export the private key (as we can use the same key in another POD).

    I am aware that we can export the public key. This question is in regard to the private key.

    Version:
    R13 19B

    Best Comment

    Glen Ryen

    Hi Ryan,

    Not possible, only the public SSH key can be exported from Oracle.  You'd have to generate the SSH key pair outside of Oracle and then import the private key into the POD(s).

    Hope that helps,

    Glen

    Comment

     

    • Glen Ryen

      Hi Ryan,

      Not possible, only the public SSH key can be exported from Oracle.  You'd have to generate the SSH key pair outside of Oracle and then import the private key into the POD(s).

      Hope that helps,

      Glen

    • Becky Alvarez

      We do allow you to export and import wallets that contain all keys that include both public and private keys.  This is used when you do production and test data refreshes.

      • Ryan Tilles

        That could be useful. How's that done, as I'm not seeing an obvious ESS job?

        Also, you said "data" refreshes? Is there a way to just refresh data and leave configs as-is? I ask because 1) this would be news to me and 2) if you do a full P2T, I'd think it brings over the wallet anyway, so not sure why you'd need to export the wallet.

        • Lakshmish Rao

          Please refer to below KM

          Payments Wallet Migration Post P2T / T2T Refresh (Doc ID 2407678.1)

          Regards,
          Rao

          • Ryan Tilles

            Thanks. I was familiar with the "Import Security Credentials Job", but didn't expect an export process to be within it (since the job is explicitly called "Import").

            Can you clarify Becky's "data refresh" comment?

    • Becky Alvarez

      Copied directly from the note: 

      "P2T process does not copy the contents of the keystore from source to the target environment. So, if the source environment was encrypted or had a Payment system key setup in place then the Payments wallet contents need to be manually copied over from the source environment into the target environment. Starting with REL13.18.02 (PB6), Payments has made this manual task self serviceable and eliminates the need to engage cloud operations."

      Hope that answers your question.