Project

General

Profile

Actions

Bug #1916

closed

LDAP Authentication ignores user naming attribute

Added by c c almost 14 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
User Manager / Privileges
Target version:
-
Start date:
09/28/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

Using a User Naming Attribute other than CN does not appear to work. Additionally, LDAP authentication (both Diags-->Authentication, and OpenVPN client auth) seems to ignore "" and anything after an symbol (that is, user "test" is considered the same as "").

Steps to reproduce:
1) setup an LDAP server. Add user cn=test, with attribute "mail=".
2) Set up pfSense to authenticate against that server.
3) Go to diags-->Authentication. Try to authenticate both as username "test", and as username "test@thisisnonsense". Note how either one works.
4) Change the user naming attribute to "mail".
5) test authentication again, this time with username "".

Expected result:
pfSense should properly authenticate the user by the selected attribute.

What actually happens:
Presumably because @ signs are being ignored, the user is not found and authentication fails.

Tested on pfSense 2.0 in a virtual environment (amd64).

Actions #1

Updated by Chris Buechler almost 14 years ago

  • Category set to User Manager / Privileges
  • Target version set to 2.0.1
  • Affected Version set to 2.0
Actions #2

Updated by Chris Buechler over 13 years ago

  • Target version deleted (2.0.1)
Actions #3

Updated by Kill Bill over 8 years ago

Certainly works just fine now.

Actions #4

Updated by Jim Pingle over 8 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF