Closed GoogleCodeExporter closed 8 years ago
JAP_SSH uses the SSH protocol
JAP_SSH supports 2 authentication methods:
1) authentication with a username and password:
REMOTE_PROXY_SERVERS/AUTHENTICATION/USERNAME
REMOTE_PROXY_SERVERS/AUTHENTICATION/PASSWORD
2) authentication with a username and a RSA/DSA key:
REMOTE_PROXY_SERVERS/AUTHENTICATION/USERNAME
LOCAL_PROXY_SERVER/KEYS/PUBLIC/FILE
LOCAL_PROXY_SERVER/KEYS/PRIVATE/FILE
LOCAL_PROXY_SERVER/KEYS/PRIVATE/PASSPHRASE
you can have more than one RSA/DSA key (identity)
JAP_SSH authenticates the SSH server with the server fingerprint:
REMOTE_PROXY_SERVERS\KEY\AUTHENTICATION\FINGERPRINT
JAP_WS uses the HTTP and HTTPS protocol (HTTPS uses AES-256)
JAP_WS supports 1 authentication method:
1) authentication with a username and password:
REMOTE_PROXY_SERVERS/AUTHENTICATION/USERNAME
REMOTE_PROXY_SERVERS/AUTHENTICATION/PASSWORD
JAP_WS authenticates the server certificate with the authority which has signed
the server certificate:
REMOTE_PROXY_SERVERS\CERTIFICATE\AUTHENTICATION\FILE
if you do not configure a certificate authority, JAP_WS will use the default
certificate authorities installed with node/python. so, unless the server uses
a self-signed certificate, or a certificate that is signed with a non-default
certificate authority, you do not have to configure a certificate authority
yourself.
both DOTCLOUD and OPENSHIFT use certificates signed by default certificate
authorities.
Original comment by jeroen.v...@gmail.com
on 28 Dec 2012 at 10:08
Original comment by goknmuse
on 23 Jan 2013 at 9:23
Original issue reported on code.google.com by
siukun89
on 25 Dec 2012 at 1:04