Dialog: Subversion Authentication

The dialogs are used to authenticate 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://: Native 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)
- Alternatively or in addition to the user name and password prompt, the client could also be authenticated with "client certificates" (for TLS/SSL encryption). (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
- Alternatively or in addition to the user name and password, the client could also be authenticated with "client certificates".
  The dialogs for authentication open with the client certificate.
svn+ssh://: Native 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 a server certificate in the dialog for authentication, if the server is still unknown, in order to be sure that it is the correct server

Dialog for authentication with a server certificate

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.

Authentication area

Connection which is secured

Example: https://svn repository:443

Table 43. Certificate information (for SSL/TLS connections)

Host name	Example: `svn repository`
Thumbprint
Valid from
Valid to
Issuer	Example: `CODESYS GmbH`
Certificate

Table 44. SSH server key information (for SSH connections)

Key type
Key size (bits)
Key thumbprint

Save information to RAM

standard icon : The certificate is saved to the working memory. Then the client recognizes in the current CODESYS session for future connections.

When you restart CODESYS, you have to accept the certificate again.

Save to disk

standard icon : The certificate is saved on the computer and it is available for future connections.

When you restart CODESYS, the saved certificate is used.

OK	Authenticates and established the connection

Tip

The certificate store is secured cryptographically and distributed with other SVN clients.

Dialog for authentication with a client certificate

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.

Authentication area

Connection which is secured

Example: https://svn repository:443

Table 45. The SSL server requires a client certificate file.

File	Client certificate file

Save information to RAM

standard icon : The certificate is saved to the working memory. Then the client recognizes in the current CODESYS session for future connections.

When you restart CODESYS, you have to accept the certificate again.

Save to disk

standard icon : The certificate is saved on the computer and it is available for future connections.

When you restart CODESYS, the saved certificate is used.

OK	Authenticates and established the connection

Dialog for authentication with a passphrase

Initial situation: The SVN server is configured so that it demands a client certificate for authentication. The applied certificate is protected by a passphrase.

Authentication area

Connection which is secured

Example: https://svn repository:443

Table 46. A password is needed to unlock the certificate.

Passphrase

Example: ***

Save information to RAM

standard icon : The passphrase is saved to the working memory. Then the client recognizes in the current CODESYS session for future connections.

When you restart CODESYS, you have to accept the certificate again.

Save to disk

standard icon : The passphrase is saved on the computer and it is available for future connections.

When you restart CODESYS, the saved certificate is used.

OK	Authenticates with client certificates by means of a passphrase and establishes the connection

Dialog for authentication with a user name and password

Initial situation: The SVN server is configured so that it demands a user name and password for authentication.

Authentication area

Connection which is secured

Example: https://svn repository:443

User name	Example: `a.mayr`
Password	Example: `***`

Save information to RAM

standard icon : Saved to the working memory

Then the client recognizes in the current CODESYS session for future connections.

When you restart CODESYS, you have to accept the certificate again.

Save to disk

standard icon : Saved on the computer and it is available for future connections

When you restart CODESYS, the saved certificate is used.

OK	Establishes the connection and authenticates it