Skip to content

Commit a47528e

Browse files
authored
Merge pull request #204251 from stegag/patch-32
Update point-to-site-vpn-client-configuration-radius-other.md
2 parents 87bbc7d + ada58cd commit a47528e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/vpn-gateway/point-to-site-vpn-client-configuration-radius-other.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The configuration workflow for P2S RADIUS authentication is as follows:
3434
>If there are any changes to the point-to-site VPN configuration after you generate the VPN client configuration profile, such as the VPN protocol type or authentication type, you must generate and install a new VPN client configuration on your users' devices.
3535
>
3636
37-
To use a different authentication type (for example, OTP), or to use a different authentication protocol (such as PEAP-MSCHAPv2 instead of EAP-MSCHAPv2), you must create your own VPN client configuration profile. To create the profile, you need information such as the virtual network gateway IP address, tunnel type, and split-tunnel routes. You can get this information by using the following steps.
37+
To use a different authentication type (for example, OTP), or to use a different authentication protocol (such as PEAP-MSCHAPv2 instead of EAP-MSCHAPv2), you must create your own VPN client configuration profile. If you have Point to Site VPN configured with RADIUS and OpenVPN, currently PAP is only authentication method supported between the gateway and RADIUS server. To create the profile, you need information such as the virtual network gateway IP address, tunnel type, and split-tunnel routes. You can get this information by using the following steps.
3838

3939
## Generate VPN client configuration files
4040

0 commit comments

Comments
 (0)