[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
LDAP and X.500 like attribute flattening or attribute inheritance
- To: openldap-general@openldap.org
- Subject: LDAP and X.500 like attribute flattening or attribute inheritance
- From: Stuart Schmukler <Stuart.Schmukler@ncal.kaiperm.org>
- Date: 19 Oct 1998 18:05:59 -0700
- Alternate-recipient: Allowed
- Content-identifier: 0410C362BE1F703D
- Content-return: Allowed
- Conversion: Allowed
- Disclose-recipients: Prohibited
- Original-encoded-information-types: IA5-Text
- X400-content-type: P2-1988 ( 22 )
- X400-mts-identifier: [/c=US/admd= /prmd=kaiperm/; 0410C362BE1F703D-ncalMTA]
- X400-originator: Stuart.Schmukler@ncal.kaiperm.org
- X400-received: by mta ncalMTA in /c=US/admd= /prmd=kaiperm/; Relayed; 19 Oct 1998 18:05:59 -0700
- X400-received: by /c=US/admd= /prmd=kaiperm/; Relayed; 19 Oct 1998 18:05:59 -0700
- X400-recipients: non-disclosure;
Is there a standard way to get X.500 flattening of attributes in LDAP servers? By flattening, I mean
attributes stored at nodes higher in the tree appearing when a lower level node is retreived (assuming
that the lower mode hasn't defined the attribute.)
I have some hierarchical attributes that may 'live' in any of a number of places in the
organizational tree. When I find a DN I want them to appear to be in the DN's attribute set.
SaS