The dialogs are used for authenticating the server/client connection. A server or client authentication is performed depending on the initial situation and protocol.
Overview of possible protocols and dialogs
svn://
: The SVN protocol; either unencrypted or SSL/TLS encrypted
Can prompt for user name and password (even for an unencrypted connection)
Can prompt for a server certificate from the dialog for authentication in order to confirm the server if a certificate is unknown, defective, or invalid (for TLS/SSL encryption)
As an alternative or in addition to the user name and password prompt, the client can also be authenticated with client certificates (for TLS/SSL encryption). The dialogs for authentication open with the client certificate.
http://
: SVN via http, unencrypted
Can prompt for user name and password
https://
: SVN via http, SSL/TLS encrypted.
Can prompt for user name and password
Can prompt for a server certificate from the dialog for authentication in order to confirm the server if a certificate is unknown, defective, or invalid.
As an alternative or in addition to the user name and password, the client can also be authenticated with client certificates. The dialogs for authentication open with the client certificate.
svn+ssh://
: The SVN protocol, encrypted through an SSH tunnel. SSH (Secure Shell) is the usual networking tool in Linux/Unix for accessing other computers.
Can prompt for user name and password
Prompts for server certificate in the dialog for authentication if the server is still unknown in order to be sure that it is the correct server.
Initial situation: CODESYS (as a client) receives an unknown or defective server certificate.
This dialog shows information about the certificate. There you can confirm the identity of the server.
Host name |
Example: |
Thumbprint |
|
Valid from |
|
Valid to |
|
Issuer |
Example: |
Certificate |
Save information to RAM |
If you restart CODESYS, then you have to accept the certificate again. |
Save to disk |
If you restart CODESYS, then the saved certificate is used. |
The certificate memory is secured cryptographically and distributed with other SVN clients.
See also
Initial situation: The SVN server requires a client certificate for authentication.
In this dialog, you select the client certificate in order to confirm the identity.
Save information to RAM |
If you restart CODESYS, then you have to accept the certificate again. |
Save to disk |
If you restart CODESYS, then the saved certificate is used. |
Initial situation: The SVN server is configured so that it demands a client certificate for authentication. The applied certificate is protected by a pass phrase.
Save information to RAM |
If you restart CODESYS, then you have to accept the certificate again. |
Save to disk |
If you restart CODESYS, then the saved certificate is used. |
Initial situation: The SVN server is configured so that it demands a user name and password for authentication.
Save information to RAM |
If you restart CODESYS, then you have to accept the certificate again. |
Save to disk |
If you restart CODESYS, then the saved certificate is used. |