---
title: Before you begin configuring a RADIUS gateway
description: Review these prerequisites before setting up a RADIUS gateway in PingOne.
component: pingone
page_id: pingone:integrations:p1_radius_gateway_prereqs
canonical_url: https://docs.pingidentity.com/pingone/integrations/p1_radius_gateway_prereqs.html
revdate: July 30, 2024
section_ids:
  prerequisites: Prerequisites
  docker: Docker
  system-requirements: System requirements
  gateway-access: Gateway access
  pingone-user-privileges: PingOne user privileges
---

# Before you begin configuring a RADIUS gateway

Before you start setting up a gateway, ensure that you have the following information.

## Prerequisites

To enable communication between PingOne Remote Authentication Dial-In User Service (RADIUS) *(tooltip: \<div class="paragraph">
\<p>A client/server networking protocol providing centralized user management.\</p>
\</div>)* gateway and your RADIUS clients, you'll need:

* To add the PingOne DaVinci service to your PingOne environment.

* A RADIUS Client IP and Shared Secret for each RADIUS client.

* A DaVinci flow with a DaVinci policy. You should add the RADIUS gateway connector, the PingID connector, and use an out-of-the-box RADIUS gateway flow. Learn more in the [PingOne RADIUS gateway connector](https://docs.pingidentity.com/connectors/p1_radius_gateway_connector.html) documentation. Learn more about PingOne DaVinci policies in [DaVinci flow policies](https://docs.pingidentity.com/davinci/applications/davinci_flow_policies.html).

* (Optional) If you want to perform multi-factor authentication (MFA) *(tooltip: \<div class="paragraph">
  \<p>An electronic authentication method where a user is granted access only after presenting two or more verification factors for authentication.\</p>
  \</div>)* using PingID, you'll also need to configure the RADIUS gateway in a PingOne environment that has PingID linked as a service.

* RADIUS gateway currently supports PAP, MS-CHAP v2, and EAP-MSCHAPv2 protocols. If you want to use the MS-CHAP v2, or EAP-MS-CHAP v2 protocol, you need a Network Policy Server (NPS). You'll also need to enable users to enter an one-time passcode (OTP) *(tooltip: \<div class="paragraph">
  \<p>A passcode valid for only one sign-on or transaction on a computer system or other digital device. Also known as a one-time password, one-time PIN, or dynamic password.\</p>
  \</div>)* with their username. Learn more in [Enable users to enter an OTP with their username in MS-CHAP v2, or EAP-MSCHAPv2 mode](p1_enable_users_to_enter_otp_with_username.html).

* (Optional) When using the PAP protocol, you can also incorporate an NPS into a flow.

## Docker

You can run the gateway in a Docker container or as a standalone Java application. If you plan to run the gateway in a Docker container, ensure that you have Docker installed on the computer that will run the gateway.

## System requirements

The computer, virtual machine, or Docker environment that will run the gateway should have the following resources dedicated to the gateway:

* Processor: 2 CPUs or virtual CPUs

* RAM: 1 GB

* Storage: 1 GB

## Gateway access

The gateway requires access to the RADIUS client over the network as well as the ability to initiate outbound requests over the internet to establish a WebSocket Secure connection to PingOne.

The WebSocket Secure address varies depending on your geography. Ensure that the gateway can access the WebSocket Secure address for your geography.

| Geography                                                                   | Address                                                                                                           |
| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Australia                                                                   | wss\://gateways.pingone.com.au/wss\://gateways-ap-southeast-2.pingone.com.au/                                     |
| Canada                                                                      | wss\://gateways.pingone.ca/wss\://gateways-ca-central-1a.pingone.ca/wss\://gateways-ca-central-1b.pingone.ca/     |
| Europe                                                                      | wss\://gateways.pingone.eu/wss\://gateways-eu-central-1.pingone.eu/wss\://gateways-eu-west-1.pingone.eu/          |
| North America (US)                                                          | wss\://gateways.pingone.com/wss\://gateways-us-east-2.pingone.com/wss\://gateways-us-west-2.pingone.com/          |
| Singapore                                                                   | wss\://gateways.pingone.sg/wss\://gateways-ap-southeast-1y.pingone.sg/wss\://gateways-ap-southeast-1z.pingone.sg/ |
| Asia Pacific (legacy)&#xA;&#xA;Available only for existing .asia customers. | wss\://gateways.pingone.asia/wss\://gateways-ap-southeast-2.pingone.asia/                                         |

## PingOne user privileges

The administrator setting up the gateway should have the `Environment admin` role. To confirm, open the PingOne console, locate the administrator identity, and confirm its roles.