Absent Member.. Lim Swee Aun Absent Member..
Absent Member..
1636 views

ssh key based login

Jump to solution

Hi,

 

Customer uses public/private key pairs for their ssh access to Linux systems.

a. How to configure OO flows (running ssh scripts) to use keys?

 

in other words:

b.how to setup public/private key pair between OO and Linux system, so that no username/password is needed?

 

Additional info:

I have managed to configure putty in OO server - on Windows Svr,

to use these keys, so I can putty to target RedHat server without username/login

(by setting up public/private key between putty and RedHat).

 

Thanks,

SweeAun LIM

BSA PreSales, Singapore.

 

Labels (1)
Tags (1)
0 Likes
1 Solution

Accepted Solutions
Daniel_Linsley Absent Member.
Absent Member.

Re: ssh key based login

Jump to solution

Hello,

 

First make sure the key generated form PuttyGen is type SSH-2 RSA or SSH-2 DSA.  The SSH-1 RSA is not supported.

 

Copy and paste the public key somewhere, you'll need it on the target RedHat server.  Add the string to the .ssh/authroized_keys file of the desired user's home directory.

 

Export the private key from PuttyGen with the Conversions menu -> "Export OpenSSH Key"

 

Place this file on the RAS. For the privateKeyFile input, specify the path to this file. User's username is still required. When a privateKeyFile is specified, the password input becomes the passphrase input for the private key file. If no passphrase was specified for the key file, anything can be used in the input.

 

Dan.

5 Replies
Daniel_Linsley Absent Member.
Absent Member.

Re: ssh key based login

Jump to solution

Hello,

 

First make sure the key generated form PuttyGen is type SSH-2 RSA or SSH-2 DSA.  The SSH-1 RSA is not supported.

 

Copy and paste the public key somewhere, you'll need it on the target RedHat server.  Add the string to the .ssh/authroized_keys file of the desired user's home directory.

 

Export the private key from PuttyGen with the Conversions menu -> "Export OpenSSH Key"

 

Place this file on the RAS. For the privateKeyFile input, specify the path to this file. User's username is still required. When a privateKeyFile is specified, the password input becomes the passphrase input for the private key file. If no passphrase was specified for the key file, anything can be used in the input.

 

Dan.

Srinivaslogic
Visitor.

Re: ssh key based login

Jump to solution

Hi All, I am getting a invalid keyFilePath error. Manually I can able to login but using SSH Shell operator getting the error.

Regards,

Sri

0 Likes
ChuckP Absent Member.
Absent Member.

Re: ssh key based login

Jump to solution

Sri,

I was having the same issue running HPOO 10.22.  The solution was installing PPK file on the Central server.  Works fine.  However, what I'm still unable to get working is using a passphrase with key.  I read that the passphrase is entered in the password field if you have key specified but I cannot get key authentication to work with a passphrase.

-Chuck

0 Likes
Srinivaslogic
Visitor.

Re: ssh key based login

Jump to solution

Chuck,

I am able to run the flows with the keys.

You need to convert the ppk file into Openssh using putty generator, and place that file in RAS.

After that you can able to execute the flows with passphrase.

Regards,

Sri

0 Likes
Super Contributor.. Chuck Perilli Super Contributor..
Super Contributor..

Re: ssh key based login

Jump to solution

I learned the private key needs to be installed on BOTH central and RAS servers.  I ran the same flow several times and sometimes it ran from central and sometimes from RAS.  

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.