Question

12
Replies
222
Views
StefanoCimmino Member since 2012 14 posts
NTT Data Italia S.p.A.
Posted: 2 years ago
Last activity: 2 years 1 month ago
Closed
Solved

SFTP Connector : No Configuration was registered that can handle the configuration named com.sun.security.jgss.krb5.initiate

Hi,

I am calling SFTP server with Public and Server Key exchange. The connection fails, in the trace I see :

No Configuration was registered that can handle the configuration named com.sun.security.jgss.krb5.initiate.

In the Log file I see :

Adding server fingerprint to repository: 83:cc:5d:8e:ca:7c:df:a0:3e:78:31:91:91:83:2b:47
Connecting to xx.xx.xx.xx port 22
Connection established
Remote version string: SSH-2.0-OpenSSH_7.4
Local version string: SSH-2.0-JSCH-0.1.54
CheckCiphers: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-ctr,arcfour,arcfour128,arcfour256
CheckKexes: diffie-hellman-group14-sha1,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521
CheckSignatures: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
SSH_MSG_KEXINIT sent
SSH_MSG_KEXINIT received
kex: server: curve25519-sha256,curve25519-sha256@xx.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
kex: server: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
kex: server: chacha20-poly1305@xx.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
kex: server: chacha20-poly1305@xx.com,aes256-gcm@xx.com,aes128-gcm@xx.com,aes256-ctr,aes192-ctr,aes128-ctr
kex: server: hmac-sha2-512-etm@xx.com,hmac-sha2-256-etm@xx.com,hmac-ripemd160-etm@xx.com,umac-128-etm@xx.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160,umac-128@xx.com
kex: server: hmac-sha2-512-etm@xx.com,hmac-sha2-256-etm@xx.com,hmac-ripemd160-etm@xx.com,umac-128-etm@xx.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160,umac-128@xx.com
kex: server: none,zlib@xx.com
kex: server: none,zlib@xx.com
kex: server:
kex: server:
kex: client: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
kex: client: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
kex: client: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc
kex: client: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc
kex: client: hmac-md5,hmac-sha1,hmac-sha2-256,hmac-sha1-96,hmac-md5-96
kex: client: hmac-md5,hmac-sha1,hmac-sha2-256,hmac-sha1-96,hmac-md5-96
kex: client: none
kex: client: none
kex: client:
kex: client:
kex: server->client aes128-ctr hmac-sha2-256 none
kex: client->server aes128-ctr hmac-sha2-256 none
SSH_MSG_KEX_ECDH_INIT sent
expecting SSH_MSG_KEX_ECDH_REPLY
ssh_rsa_verify: signature true
Checking for fingerprint in repository: 83:cc:5d:8e:ca:7c:df:a0:3e:78:31:91:91:83:2b:47
Found fingerprint in repository: 83:cc:5d:8e:ca:7c:df:a0:3e:78:31:91:91:83:2b:47
Host '10.25.173.84' is known and matches the RSA host key
SSH_MSG_NEWKEYS sent
SSH_MSG_NEWKEYS received
SSH_MSG_SERVICE_REQUEST sent
SSH_MSG_SERVICE_ACCEPT received
Authentications that can continue: gssapi-with-mic,publickey,keyboard-interactive,password
Next authentication method: gssapi-with-mic
Disconnecting from xx.xx.xx.xx port 22
FTP connection failed

Why Pega try to use only "gssapi-with-mic" and doesn't continue with "publickey"?

I am using Pega 7.3.1.

Could you help me?

Thanks,

Stefano.

Data Integration SR Created
Moderation Team has archived post
Share this page LinkedIn