Predefined strings that can be used to configure the Secure Transport plugin through the Property QoS Policy of the DomainParticipant. More...

Predefined strings that can be used to configure the Secure Transport plugin through the Property QoS Policy of the DomainParticipant.

The following tables list the supported Secure Transport properties.

*Properties for Registering the Secure Transport*
Property Name	Description	Required?
dds.transport.load_plugins	Comma-separated strings indicating the prefix names of all plugins that will be loaded by RTI Connext. Up to 8 plugins may be specified. For example, "dds.transport.DTLS.dtls1". In the following examples, <DTLS_prefix> indicates the string that is used as a prefix in the property names for all the settings that are related to this DTLS tranpsort plugin. <DTLS_prefix> must begin with "dds.transport." (such as "dds.transport.DTLS.dtls1").	YES
<DTLS_prefix>.library	Must set to "libnddstransporttls.so" (for Linux systems) or "nddstransporttls.dll" (for Windows). This library (and the dependent openssl libraries) needs to be in the library search path used by RTI Connext during run time (pointed to by the environment variable LD_LIBRARY_PATH on Linux systems, DYLD_LIBRARY_PATH on macOS systems, or Path on Windows systems)	Only if linking dynamically
<DTLS_prefix>.create_function	Must be set to "NDDS_Transport_DTLS_create" .	Only if linking dynamically
<DTLS_prefix>.create_function_ptr	Defines the function pointer to the DTLS Transport Plugin creation function. Used for loading DTLS Transport Plugin statically. Must be set to the NDDS_Transport_DTLS_create() function pointer.	Only if linking statically
<DTLS_prefix>.aliases	Used to register the transport plugin returned by NDDS_Transport_DTLS_create() (as specified by <DTLS_prefix>.create_function) to the domain participant. Refer to aliases_in parameter in NDDS_Transport_Support_register_transport() for details. Aliases should be specified as comma separated string, with each comma delimiting an alias. If it is not specified, <DTLS_prefix> is used as the default alias for the plugin	NO
<DTLS_prefix>.network_address	Refer to network_address_in parameter in NDDS_Transport_Support_register_transport(). This value overwrite the value returned by the output parameter in NDDS_Transport_create_plugin function as specified in "<DTLS_prefix>.create_function".	NO
<WAN_prefix>.verbosity	Set to a number specifying the verbosity of log messages from the transport. Possible values include: -1: silent 0 (default): errors only 1: errors and warnings 2: local status 5 or higher: all messages	NO
<DTLS_prefix>.parent.address_bit_count	See NDDS_Transport_Property_t::address_bit_count Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_DTLS_PROPERTY_DEFAULT for the default value.	NO
<DTLS_prefix>.parent.properties_bitmap	See NDDS_Transport_Property_t::properties_bitmap Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_DTLS_PROPERTY_DEFAULT for the default value.	NO
<DTLS_prefix>.parent.gather_send_buffer_count_max	See NDDS_Transport_Property_t::gather_send_buffer_count_max Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_DTLS_PROPERTY_DEFAULT for the default value.	NO
<DTLS_prefix>.parent.message_size_max	See NDDS_Transport_Property_t::message_size_max Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_DTLS_PROPERTY_DEFAULT for the default value.	NO
<DTLS_prefix>.parent.allow_interfaces	See NDDS_Transport_Property_t::allow_interfaces_list and NDDS_Transport_Property_t::allow_interfaces_list_length. Interfaces should be specified as comma-separated strings, with each comma delimiting an interface. For example, "127.0.0.1,eth0" Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_DTLS_PROPERTY_DEFAULT for the default value.	NO
<DTLS_prefix>.parent.deny_interfaces	See NDDS_Transport_Property_t::deny_interfaces_list and NDDS_Transport_Property_t::deny_interfaces_list_length. Interfaces should be specified as comma-separated strings, with each comma delimiting an interface. For example, "127.0.0.1,eth0" Refer to NDDS_Transport_WAN_Plugin::NDDS_TRANSPORT_DTLS_PROPERTY_DEFAULT for the default value.	NO
<DTLS_prefix>.send_socket_buffer_size	See NDDS_Transport_DTLS_Property_t::send_socket_buffer_size	NO
<DTLS_prefix>.recv_socket_buffer_size	See NDDS_Transport_DTLS_Property_t::recv_socket_buffer_size	NO
<DTLS_prefix>.ignore_loopback_interface	See NDDS_Transport_DTLS_Property_t::ignore_loopback_interface	NO
<DTLS_prefix>.ignore_nonrunning_interfaces	See NDDS_Transport_DTLS_Property_t::ignore_nonrunning_interfaces	NO
<DTLS_prefix>.transport_priority_mask	See NDDS_Transport_DTLS_Property_t::transport_priority_mask	NO
<DTLS_prefix>.transport_priority_mapping_low	See NDDS_Transport_DTLS_Property_t::transport_priority_mapping_low	NO
<DTLS_prefix>.transport_priority_mapping_high	See NDDS_Transport_DTLS_Property_t::transport_priority_mapping_high	NO
<DTLS_prefix>.recv_decode_buffer_size	See NDDS_Transport_DTLS_Property_t::recv_decode_buffer_size	NO
<DTLS_prefix>.port_offset	See NDDS_Transport_DTLS_Property_t::port_offset	NO
<DTLS_prefix>.dtls_handshake_resend_interval	See NDDS_Transport_DTLS_Property_t::dtls_handshake_resend_interval	NO
<DTLS_prefix>.dtls_connection_liveliness_interval	See NDDS_Transport_DTLS_Property_t::dtls_connection_liveliness_interval	NO
<DTLS_prefix>.tls.verify.ca_file	See NDDS_Transport_TLS_Verification::ca_file	either ca_file or ca_path is required.
<DTLS_prefix>.tls.verify.ca_path	See NDDS_Transport_TLS_Verification::ca_path	either ca_file or ca_path is required.
<DTLS_prefix>.tls.verify.verify_depth	See NDDS_Transport_TLS_Verification::verify_depth	NO
<DTLS_prefix>.tls.verify.verify_peer	See NDDS_Transport_TLS_Verification::verify_peer	NO
<DTLS_prefix>.tls.verify.verify_callback	See NDDS_Transport_TLS_Verification::callback This can be set to one of three values: "default" selects the default callback NDDS_Transport_TLS_default_verify_callback() "verbose" selects the verbose callback NDDS_Transport_TLS_verbose_verify_callback() "none" requests no callback be registered	NO
<DTLS_prefix>.tls.cipher.cipher_list	See NDDS_Transport_TLS_Ciphers::cipher_list	NO
<DTLS_prefix>.tls.cipher.ciphersuites	See NDDS_Transport_TLS_Ciphers::ciphersuites	NO
<DTLS_prefix>.tls.cipher.dh_param_files	See NDDS_Transport_TLS_Ciphers::dh_param_files. For example: "foo.h:512,bar.h:256" means dh_param_files[0].file = foo.h, dh_param_files[0].bits = 512, dh_param_files[1].file = bar.h, dh_param_files[1].bits = 256,	NO
<DTLS_prefix>.tls.cipher.engine_id	See NDDS_Transport_TLS_Ciphers::engine_id	NO
<DTLS_prefix>.tls.identity.certificate_chain_file	See NDDS_Transport_TLS_Identity::certificate_chain_file	YES
<DTLS_prefix>.tls.identity.private_key_password	See NDDS_Transport_TLS_Identity::private_key_password	NO
<DTLS_prefix>.tls.identity.private_key_file	See NDDS_Transport_TLS_Identity::private_key_file	NO
<DTLS_prefix>.tls.identity.rsa_private_key_file	See NDDS_Transport_TLS_Identity::rsa_private_key_file	NO