Hello Steve (and others interested in LDAP) -
Further to my previous posting, Mike has added support for a complete search
definition in a patched version of AuthBy LDAP2 for Radiator 2.16.1.
Steve - would you be interested in testing this for us prior to it being
included in the next release?
Hello Steve -
On Fri, 07 Jul 2000, Felicetti, Stephen A. wrote:
>
> Running Radiator 2.15 under Sun OS 5.6 against Netscape LDAP 3.11, Cisco
> AS5300 as the access server.
>
> I'm using the AuthAttrDef function to limit those that can have access to
> our system after connecting to the AS.
> A
Running Radiator 2.15 under Sun OS 5.6 against Netscape LDAP 3.11, Cisco
AS5300 as the access server.
I'm using the AuthAttrDef function to limit those that can have access to
our system after connecting to the AS.
As long as the altmail5 attribute exists in the user's entry, I can permit
or deny
Radiator only knows how to deal with attribute/value pairs as defined in the
dictionary that is in use. In your example above, "Xstring" is not defined
in
your dictionary, so there is no match.
>>I already have the Xstring attributed added to the default dictionary
file.
>>It looks like this:
>
Hello Stephen -
On Fri, 10 Mar 2000, Felicetti, Stephen A. wrote:
> Hey guys...
>
> I'd like to know if it is possible to use AuthAttrDef in the following
> scenario:
>
> I have an LDAP server. I'd like to have an attribute called remoteuser.
> Valid assignments
> to this attribute would be y
Hey guys...
I'd like to know if it is possible to use AuthAttrDef in the following
scenario:
I have an LDAP server. I'd like to have an attribute called remoteuser.
Valid assignments
to this attribute would be yes, or no.
I have a Cisco AS5300. It sends an Access-Request to Radiator with only t
