Allows to configure if current Vortex Library instance will accept TLS incoming connections.
While using TLS under BEEP, as a peer protocol, any instance running could receive a TLS request for its activation. This function allows to configure if such request will be allowed or recognized.
Default TLS configuration is to not allow receive a TLS request.
This function doesn't disable the possibility to connect to a remote peer and request to negotiate the TLS security transport.
There are two typical scenarios:
- 1. Vortex Library client applications doesn't call this function, so any other BEEP peer, that the client instance connects to, can't request to activate TLS transport. But Vortex Library client could issue a call to vortex_tls_start_negociation to enable TLS transport against a BEEP peer accepting TLS requests. In the case the remote peer is running Vortex Library, that peer have already issued a call to vortex_tls_accept_negociation.
- 2. In the other hand, Vortex Library listeners could enable accepting TLS incoming connections so they publish as a possible profile the TLS one. This is done by calling to this function. This action enables the possibility to receive a TLS request to secure the connection.
This function allows to define several handlers to configure the TLS support. This handler are defined per profile which means they are global to all TLS profile request received.
|accept_handler ||A handler executed to notify user app level that a TLS request was received, allowing to accept or deny it according to the value returned by the handler. You can use NULL value for this parameter. This will make Vortex Library to set the default accept handler which always accept every TLS negotiation.|
|certificate_handler ||A handler executed to know where is located the certificate file to be used to cipher the session. You can use NULL value for this parameter. This will make Vortex Library to set the default certificate handler which returns a path to a test certificate. It is highly recommended to set this handler, however you can use NULL value under development environment.|
|private_key_handler ||A handler executed to know where is located the private key file to be used to cipher the session. You can use NULL value for this parameter. This will make Vortex Library to set the default private key handler which returns a path to the test private key. It is highly recommended to set this handler, however you can use NULL values under development environment.|
- Returns it the current server instance could accept incoming TLS connections.