dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorEngineering interfaces and toolsdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorProfessional Version Controldl-breadcrumb-item__separatorReference, User Interfacedl-breadcrumb-item__separatorDialogsdl-breadcrumb-item__separatorDialog 'Subversion Authentication'
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Dialog 'Subversion Authentication'dl-permalink__symbolPermalink

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.

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 that is secured

Example: ‎https://svn repository:443‎
Table 900: “Certificate information” (for SSL/TLS connections)

“Host name”

Example: ‎svn repository‎

“Thumbprint”

“Valid from”

“Valid to”

“Issuer”

Example: ‎ABB AG‎

“Certificate”
Table 901: “SSH server key information” (for SSH connections)

“Key type”

“Key size (bits)”

“Key thumbprint”

“Save information to RAM”

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

If you restart CODESYS, then you have to accept the certificate again.

“Save to disk”

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

If you restart CODESYS, then the saved certificate is used.

“OK”

Authenticates and established the connection.

The certificate memory 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 that is secured

Example: ‎https://svn repository:443‎
Table 902: “The SSL server requires a client certificate file.”

“File”

Client certificate file

“Save information to RAM”

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

If you restart CODESYS, then you have to accept the certificate again.

“Save to disk”

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

If you restart CODESYS, then the saved certificate is used.

“OK”

Authenticates and established the connection.

Dialog for authentication with a pass phrase

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.

“Authentication area”

Connection that is secured

Example: ‎https://svn repository:443‎
Table 903: “A pass phrase is needed to unlock the certificate.”

“Pass phrase”

Example: ‎***‎

“Save information to RAM”

_cds_icon_option_activated: The pass phrase is saved to the working memory. Then the client recognizes in the current CODESYS session for future connections.

If you restart CODESYS, then you have to accept the certificate again.

“Save to disk”

_cds_icon_option_activated: The pass phrase is saved on the computer and it is available for future connections.

If you restart CODESYS, then the saved certificate is used.

“OK”

Authenticates with client certificates by means of a pass phrase 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 that is secured

Example: ‎https://svn repository:443‎

“User name”

Example: ‎a.mayr‎

“Password”

Example: ‎***‎

“Save information to RAM”

_cds_icon_option_activated: Saved to the working memory. Then the client recognizes in the current CODESYS session for future connections.

If you restart CODESYS, then you have to accept the certificate again.

“Save to disk”

_cds_icon_option_activated: Saved on the computer and it is available for future connections.

If you restart CODESYS, then the saved certificate is used.

“OK”

Establishes the connection and authenticates it.