Re: [Q] Logging to a directory

["Alex Zeltser" <alex_zeltser@securecomputing.com>]

> > We're currently working with Netscape's directory (v.4.x) and have an
> > application that needs to maintain a detailed audit trail of events
that
> > have taken place over a period of time.  The volume of events is fairly
> > high and each log entry has a fair amount of detail.
> 
> Do you mean essentially storing events in the directory in a specific
order?
> Is each event stored as a distinct object or as a value in a multi-valued
> attribute?  It'd be interesting to see the schema for something like this
> (even if it's just experimental).
> 
Nothing clever or fancy, just storing each event as a separate object with
some common sense attributes, i.e. timestamp in our own format, modifier ID
(from our system), modification type, plus a couple of other app-specific
pieces of data.

> > - Does anyone have any general words of wisdom when it comes to logging
in
> > directory-enabled apps?  Log to the directory?  Don't?  Log, but with
> > certain constraints?  Tips?
> 
> I seem to recall reading somewhere how Cisco/Microsoft (well, certainly
Cisco
> anyway) were planning to address this, by adding the concept of "events"
and a
> distinct persistent storage for volatile information (yet still using the
> same directory API?).  I need to fish around and see if I can find the
details
> again (and whether or not the details are covered by NDA)...
> 
If you could locate it and/or point me in the right direction, I'd really
appreciate it.  Others might find it useful as well.

Thanks!

Alex Zeltser