Joe H <[EMAIL PROTECTED]> wrote:
lines. lines 2 and 11 are other DEFAULT entries in the users file with
fall-through set to yes. It skips right over the SNS-Enable checkItem.
Ah. The "users" file isn't set up to do comparisons on check items.
So I don't think it will work.
Alan DeKok.
Joe H <[EMAIL PROTECTED]> wrote:
> lines. lines 2 and 11 are other DEFAULT entries in the users file with
> fall-through set to yes. It skips right over the SNS-Enable checkItem.
Ah. The "users" file isn't set up to do comparisons on check items.
So I don't think it will work.
Alan DeK
I have changed the order in which the files are processed and it didn't
change anything. I can see in the debug that it finds the attributes:
rlm_ldap: performing search in ou=people,dc=test,dc=com, with filter
(uid=test)
rlm_ldap: looking for check items in directory...
rlm_ldap: Adding radi
Joe H <[EMAIL PROTECTED]> wrote:
> Correct me if I'm wrong but that should mean, if the SNS-Enable attribute
> does not equal 1, assign the USR-Framed_IP_Address_Pool_Name and
> Idle-Timeout. I have SNS-Enable as a checkItem mapped to radiusSNSEnable
> in the ldap.attrmap.
That should be OK.
I am trying to create a new checkItem using an attribute stored in LDAP.
I would like radius to check ldap to see if the attribute exists for a
user and if it does, not assign a radiusPoolName. I have a
radiusSNSEnable attribute setup in ldap and in the dictionary files as a
check item.
I h
5 matches
Mail list logo
