cancel
Showing results for 
Search instead for 
Did you mean: 

Receiver SFTP Error : No private key with signing capability found in &&&&

Former Member
0 Kudos

Hello SFTP/PGP Experts,

Problem Statement: It is a SOAP to SFTP (with PGP encryption) Scenario, where PI needs to sign and encrypt the document and to be send to SFTP server.

Steps followed for configuration:

step 1) Followed the the document : Generating SSH Keys for SFTP Adapters - Type 2 - Process Integration - SCN Wiki for creation and configuration of keys.

Step 2) Copied the receiver's SFTP public key in .ssh folder in PI system and forwarded my public key to SFTP server team.

Step 3) Repeated step 1 to create another private key to be used for signing and created a new entry in the same view but selected the option of "Select key Pair" for signing and mentioned the previously created private key.

When I trigger the message, it fails in receiver adapter with error :: "No private key with signing capability found in '/home/x03adm/.ssh/emsapx03_rsa.key "

I tried by selecting both the private keys (I created as mentioned in above steps) in PGP configuration in Receiver SFTP Adapter.

Please see the adapter config screenshot below:

Expecting help soon!!

Thanks

Accepted Solutions (0)

Answers (3)

Answers (3)

pvishnuvardan_reddy
Active Contributor
0 Kudos

Hi Gaurav,

Also, please find below sample format of encryption and signing:

pgpapplyEncryptiontrue
pgpapplySignaturetrue
pgpownPrivateKeyprivatekey
pgppartnerPublicKeypartnerpublickey
pgppwdOwnPrivateKey******
pgpsigningAlgo

SHA1

Regards

Vishnu

sapere_jonas
Explorer

Hi there, did you ever find a solution to your problem?

If you used SXDA_TOOLS for uploading the key the encoding is changed and then creating this error!

I did the same and found out the only thing I did different was this. Trying to upload directly and then it works!

Br

pvishnuvardan_reddy
Active Contributor
0 Kudos

Hi Gaurav,

From the screen shot you have shared, I can see the private key names are different in what you have maintained in the channel and in the error you are getting.

Key maintained: emsapx03_rsakey.key

Error you are getting : No private key with signing capability found in '/home/x03adm/.ssh/emsapx03_rsa.key

Can you cross check whether the key names are correctly maintained or not.

Regards

Vishnu

Former Member
0 Kudos

Hello Vishnu,

          My bad in providing the wrong screenshot. Actually as I mentioned in my 1st post, I created 2 keys. While posting on SCN, i guess i jumbled up the screenshots.

To clear the situation, I faced same error with both the key names.

Thanks,

Gaurav

RaghuVamseedhar
Active Contributor
0 Kudos

Gaurav,

'applySignature' is missing. It seems, 'ownPrivateKey' is not properly stored. 'keyRootPath' is not pointing to correct folder.

Please check

Configuring the Encryption PGP Module

Former Member
0 Kudos

Hi Raghu,

Thanks for your response!!

     I've already applied the 'applySignature' paramter, missed to add the screenshot of all module parameters as they were not visible in single screen.

And regarding the 'keyRootPath', with same path, the SFTP communication is working fine (without PGP). So, i guess, that should not be the case for this error. And if you see the William Lee's blog, in his config also, he maintained the keys in /tmp/pgp folder.

Still looking for the solution!!

RaghuVamseedhar
Active Contributor
0 Kudos