`RDT_Base.SetTLSContext` (METH)

METHOD SetTLSContext : NBS.ERROR

Sets all the data neccessary to handle encrypted tcp connections

InOut:

Scope	Name	Type	Initial	Comment
Return	`SetTLSContext`	`NBS.ERROR`
Input	`xUseCert`	`BOOL`		If the certificate is used or not
	`psUseCaseName`	POINTER TO STRING		A name to identify this context in the security manager, the name can be completely user defined
	`ePurpose`	`NBS.PURPOSE`		This context can be used on the server side or on the client side.
	`psTLSVersion`	POINTER TO STRING		A string to select the correct protocol version
	`psCipherList`	POINTER TO NBS.CIPHER_LIST		A string to select the correct encryption cipher suites. See for example: https://www.openssl.org/docs/man1.1.1/man1/ciphers.html#CIPHER-LIST-FORMAT
	`psHostname`	POINTER TO STRING		A hostname to select the correct certificate on the server side.
	`udiVerificationMode`	`UDINT`		1 => No peer verification 2 => Active Peer verification (4) => 2+4 = 6 => Force termination, if no client certificate (8) => 2+8=10 or 2+4+8 = 14 => Request client certificate only whithin initial handshake
	`psCertCommonName`	POINTER TO STRING		A string to select the correct certificate in local certificate store It can be empty in case of an external cert handle is passed
	`hCert`	`RTS_IEC_HANDLE`	RTS_INVALID_HANDLE	External cert handle to use. Exclusive use vs cert name
	`itfCertVerifer`	`NBS.ICertificateVerifier`		A callback for application specific certificate verification

RDT_Base.SetTLSContext (METH)