[Date Prev][Date Next]
Re: how to apply shemas
On Tue, 7 Mar 2000, Christian Hammers wrote:
It's pretty easy to retype those things.
I was unaware of this draft...It seems like a fairly difficult
approach to the thing. In my RADIUS server implementation, I made
radiusAttribute be any RADIUS attribute, instead of trying to fit all
possible attributes into my schema. It makes me less likely to have to
change my schema or application to deal with it. The schema looks like
Where radiusSuperClass defines a set of defaults that this class
will be overriding. The radiusSuperClass points to the dn of another
spyRadiusEntry to extract a set of radiusAttribute attributes from (or
follow to another radiusSuperClass if you want to be sick). This
basically means I can assign a user the property of being a ``dialup
user'' and have a shared set of attributes for a dialup user, then assign
static IP addresses to users if I need.
My way may be over-simplified, but it works great for me. : )
# I want to use LDAP for RADIUS accounting/authorization and have a copy of
# the IETF draft-aboba-radius-05.txt. At the end of this draft there is
# a shema which looks like a ASN.1 notation of rules that define which
# attributes may exist in which objects.
# How to apply this in openldap? I've found a "schemacheck" in the slapd.conf
# but no config file. slapd.oc.conf looks as it would be something similar
# but it has a different notation. Is there a converter available?
# Christian Hammers WESTEND GmbH - Aachen und Dueren Tel 0241/701333-0
# email@example.com Internet & Security for Professionals Fax 0241/911879
SA, beyond.com My girlfriend asked me which one I like better.
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <firstname.lastname@example.org>
| Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________