View Issue Details

IDProjectCategoryView StatusLast Update
0002092SOGoWeb Generalpublic2012-11-06 13:47
Reporterryacketta Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status newResolutionopen 
Product Version2.0.2 
Summary0002092: LDAP uses filter instead of authenticationFilter for authentication
Description

Using the following SOGoUserSource allows one to authenticate when a member of the WTF userClass

sogod SOGoUserSources '(
{
CNFieldName = cn;
IDFieldName = uid;
UIDFieldName = uid;
authenticationFilter = "(userClass=''AE'' OR userClass=''AS'' OR userClass=''WTF'')";
baseDN = "ou=People,o=potsdam.edu";
bindAsCurrentUser = YES;
bindFields = (
uid
);
canAuthenticate = YES;
displayName = People;
filter = "(userClass=''AE'' OR userClass=''AS'' OR userClass=''WTF'')";
hostname = "ldap.potsdam.edu";
id = public;
isAddressBook = YES;
port = 389;
}

If we change filter to :

filter = "(userClass=''AE'' OR userClass=''AS'')";

Authentication fails.

According to the documentation filter is used to set a restrict lookup results and authenticationFilter is used to set a filter restriction on authentication.

TagsNo tags attached.

Activities

ludovic

ludovic

2012-11-06 13:08

administrator   ~0004778

authenticationFilter is only valid for SQL-based sources right now.

ryacketta

ryacketta

2012-11-06 13:13

reporter   ~0004779

Sorry, overlooked that tid bit.

Can we change this from a bug to a Feature please.

Issue History

Date Modified Username Field Change
2012-11-05 15:33 ryacketta New Issue
2012-11-06 13:08 ludovic Note Added: 0004778
2012-11-06 13:13 ryacketta Note Added: 0004779
2012-11-06 13:47 ludovic Severity major => feature