Skip to main content

Integrate RADIUS applications

Use this section to configure a Generic RADIUS client so it can use RADIUS authentication through IDaaS.

When to use this section​

Use this section when you need to:

  • Enable a VPN or other RADIUS client to authenticate through IDaaS.
  • Configure EAP behavior for a specific RADIUS application.
  • Reference product-specific setup instructions.

IDaaS supports RADIUS authentication and Extended Access Protocol (EAP) RADIUS authentication for RADIUS applications. EAP authentication functions as follows:

  1. A TLS tunnel is created from the VPN client (a type of RADIUS application) to the RADIUS server.
  2. Authentication is performed within that tunnel.

All communication between the VPN client and RADIUS server, including the TLS handshake and EAP messages, are packaged as RADIUS messages.

IDaaS supports two types of EAP authentication:

  1. PEAPv0 with MSCHAPv2

    This authentication protocol sends MSCHAPv2 messages over the EAP protocol. It does not support challenge messages, so only first-factor token authentication is supported.

  2. PEAPv1 with EAP-GTC

    This EAP protocol supports challenge/response and is used for two-step authentication.

The type of EAP authentication used depends on the VPN server type (that is, the RADIUS application). IDaaS lets you customize EAP settings for each RADIUS application.

note

To add or edit RADIUS applications, you must have a role with Enterprise Gateway and Agents Management View access.

Topics in this section​

note

For product-specific setup instructions, see RADIUS and VPN applications.

These pages provide setup steps and validation details for common VPN and RADIUS deployments.