Skip to content

DTLSEndPoint

Jim Schaad edited this page Jun 29, 2017 · 1 revision

DTLSEndPoint

This class is used for having a DTLS end point that can act as either a client or a server. Programs which only need client size access should use the class DTLSClientEndPoint instead.

Due to the fact the currently BouncyCastle does not support Raw Public Keys as a certificate format, only Pre-Shared Keys are supported by the system.

When an end point is created, two key sets are provided as parameters.

  • ServerKeys - is to contain the signing keys that are used by the server to authenticate itself using Raw Public Keys. All of these keys are required to have a private key.
  • UserKeys - contains all of the pre-shared and raw public keys that are authorized to create a connection.

NOTE: This API may change in the future to change how keys are checked. This will depend in part on how easy I find this to do while dealing with the OAuth Authorization framework currently being worked on in the ACE working group at the IETF.

This class inherits from the CoAPEndPoint and all of those methods and properties are available here.

Properties

No addition ones are defined

Methods

No additional ones are defined

Clone this wiki locally