The FreeRADIUS server  $Id: 15bac2a4c627c01d1aa2047687b3418955ac7f00 $
Data Structures
rlm_eap_tls.h File Reference
#include <freeradius-devel/eap/tls.h>
#include <freeradius-devel/server/base.h>
#include <freeradius-devel/server/module_rlm.h>
+ Include dependency graph for rlm_eap_tls.h:
+ This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Data Structures

struct  eap_tls_actions_t
 Cache sections to call on various protocol events. More...
struct  rlm_eap_tls_t

Data Structure Documentation

◆ eap_tls_actions_t

struct eap_tls_actions_t

Cache sections to call on various protocol events.

Definition at line 34 of file rlm_eap_tls.h.

+ Collaboration diagram for eap_tls_actions_t:
Data Fields
CONF_SECTION * recv_access_request

◆ rlm_eap_tls_t

struct rlm_eap_tls_t

Definition at line 38 of file rlm_eap_tls.h.

Data Fields
bool include_length
bool req_client_cert Whether we require the client to provide a certificate or not.

RFC 5216 says it's not mandatory, and there are some situations where it's useful to allow client access without a certificate.

fr_tls_conf_t * tls_conf Shared TLS configuration structure.
char const * tls_conf_name The name of the shared TLS configuration.
char const * virtual_server Virtual server used for validating certificates.