Product manual

NL200 Network Link Interface

In order to use TLS, the user is responsible for obtaining their own TLS Private

Key and TLS Certificate.

The following NL200 settings apply to all TLS communications in the NL200:

The TLS Settings described below cannot be edited over a

standard TCP DevConfig link. The TLS Private Key, TLS

Private Key Password and TLS Certificate can only be

edited/transmitted over a secure DevConfig link (USB or TLS).

See Section 7.4.2 for information on configuring these settings.

NOTE

TLS Status

Specifies the current status of the NL200 TLS network stack, i.e., initialized or

not initialized. The status will read “Initialized” if a TLS Private Key and TLS

Certificate are loaded in the NL200.

If the status of the TLS stack is “Initialized” then the NL200 will

automatically negotiate a secure TLS connection with

DevConfig if the Use IP Connection option is selected.

NOTE

TLS Private Key Password

Specifies the password that is used to decrypt the TLS Private Key.

This setting is only visible/editable if the DevConfig connection

is over USB or TLS.

NOTE

TLS Private Key

Specifies the private key (in PEM format) for the encryption stack.

This setting is only visible/editable if the DevConfig connection

is over USB or TLS.

NOTE

TLS Certificate

Specifies the public certificate (in PEM format) for the encryption stack.

This setting is only visible/editable if the DevConfig connection

is over USB or TLS.

NOTE

7.4.1 HTTPS

HTTPS is a protocol that provides secure identification and encrypted

communication over TCP.

In order to use HTTPS, you will need to load your TLS Private Key and TLS

Certificate into the NL200. This is done from the Settings Editor | TLS tab in

DevConfig over a USB or TLS connection these settings are not visible over a