I am able to call gpg installed on the SAP application server and run commands like --help successfully. All public keys have been trusted and the encryption works from the command prompt on the Windows server. However, when I try to encrypt a file from SAP via SM69 I receive error "skipped: No public key".
Related
I am trying to get "Run SSH Commands" step working in my local machine. I am able to SSH into a remote machine from the command line, but when I do the same with Pentaho, it returns the below error:
Does this step need any additional configuration?
Please show your configuration?
let try to use User/pass and uncheck 'Use key'.
If you want connect using private key option without password config, you need key-gen and copy key to ssh server.
I have a encryption job set, it executes just fine in Visual studio but give the following error in SSMS job agent-->
Error retrieving emailid#domain.com via WKD:No data gpg
skipped: No Data
Using SQL 2017. I tried using CMDEXEC instead of SSIS Package in job settings but it doesn't solve the problem
Arguments:
--quiet --yes --trust-model always --passphrase mypassphrase --recipient XXX#XXX.com --trust-model always --output D:\Folder\File.csv.gpg --encrypt D:\Folder\file.csv
So I was executing job from the proxy account and apparently proxy and own account is different when it comes to gpg key import. Meaning- I had imported keys using gpg/Kleopatra in my desktop using my windows credentials and was calling the job with my proxy account from job agent. Hence the proxy account was not able to access the keys. This is what solved my problem- https://superuser.com/questions/1176705/windows-account-cant-see-gpg-key#new-answer
I was trying to create integration between Jenkins and GitLab using this tutorial: https://docs.bitnami.com/aws/how-to/create-ci-pipeline/
(without Step 3: Connect Your Project With The GitLab Repository)
So I have generated public and private keys, public was added in GitLab (Settings > SSH Keys) and private key file content was inserted into text area in Jenkins Project settings (Source Code Management > Credentials > SSH Username with private key > Private key)
After that following error appeared:
what can cause such strange issue? Thanks for help :)
If you add public key to the profile of a specific GitLab user, you must:
Grant this user access to target project in GitLab.
Use username of that specific user (instead of the git username) when creating the SSH credentials in Jenkins.
I am using WinSCP to automate the copy process to server and the authentication is only with username and password.
Script is:
open username:password#ipaddress:portno -hostkey=<hostkey>
Whereas now the authentication mode has to be changed to public key.
Script changed for authenticate through public key:
open username#ipaddress:portno -privatekey=mykey.ppk
Passphrase for the private key is requested after executing the above script, but is there any way that the passphrase of the private key can be provided in the same command?
Use the -passphrase switch of the open command.
See also WinSCP FAQ
How can I connect without entering private key passphrase each time?
Also, note, that you still should use the -hostkey switch.
open username:password#ipaddress:portno -hostkey=... -privatekey=... -passphrase=...
My client provided me public key and asked me to do a ssh login. But i havent done any ssh login before. So can you please suggest me how to use public key for ssh login. I am using putty on windows
Here is a very nice tutorial on how to setup key based authentication usint putty on Windows.
http://www.ualberta.ca/CNS/RESEARCH/LinuxClusters/pka-putty.html
With SSH, public key is stored on the server and a user must have corresponding private key to log in. If this is your situation, you can specify your private key with PuTTY in one of two ways:
Configuration -> Connection -> SSH -> Auth -> Private key file for authentication
Use -i command-line option when starting PuTTY.
In both cases you need the private key in PuTTY format (.ppk). If your key is in a different format, you'll have to convert it using PuttyGen.