[Date Prev][Date Next] [Chronological] [Thread] [Top]

[ldapext] need of dynamic attributes




When a user account in a directory has expirationdate attribute,
a today's ldap application needs to write a code to check the user's expirationdate against the system's today's date
to validate if the account is valid.

If a dynamic attribute such as todaysdate is defined as a part of ldap schema and
the value of the attribute is the ldap server system's date, the application may simply configure a ldap filter something like
    (&(ou=useraccount)(todaysdate()<expirationdate)

Dynamic attributes can be quite useful, which requires such attributes and
search filter using dynamic attributes to be defined.

I wonder if work on dynamic attributes is within ldapext scope.

Any thoughts?

Thanks,


Christine Yoon
Security Integration
PricewaterhouseCoopers
(201)981-1172 (cell)
(732)706-3559

_________________________________________________________________
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.