Project

General

Profile

Actions
Copy link

Bug #7002

closed
JP

OpenVPN unable to use authentication server with ampersand in descriptive name

Bug #7002: OpenVPN unable to use authentication server with ampersand in descriptive name

Added by Anonymous almost 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Jim Pingle
Category:
OpenVPN
Target version:
2.3.3
Start date:
12/10/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.2
Affected Architecture:
All

Description

Add LDAP server in System/User Manager/Authentication Servers, include an ampersand in the Descriptive Name. Test against LDAP server in Diagnostics/Authentication, success. Configure OpenVPN server to authenticate against the LDAP server, attempt to connect with client. Server logs will show

Dec 10 23:11:15 openvpn 28595 customer_ip:1194 Peer Connection Initiated with [AF_INET]70.184.186.68:1194
Dec 10 23:11:15 openvpn 28595 customer_ip:1194 TLS Auth Error: Auth Username/Password verification failed for peer
Dec 10 23:11:15 openvpn 28595 customer_ip:1194 WARNING: Failed running command (--auth-user-pass-verify): external program exited with error status: 1
Dec 10 23:11:15 openvpn user 'test' could not authenticate.

Recreate LDAP server without ampersand in the Descriptive Name, configure OpenVPN to use new LDAP server. Attempt to connect from client, success.

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #1

  • Target version changed from Future to 2.4.0

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #2

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:c165a17e0225f09afb4882d360ba086f629f2b77.

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #3

  • Status changed from Feedback to Resolved

Works

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #4

  • Target version changed from 2.4.0 to 2.3.3
Actions
Copy link

Also available in: Atom