Re: Lag in LDAP updates

[James Mello <kingjamm@colltech.com>]

If you are on a Solaris box, take a look at the man page for nscd. It is a
nameservice cache daemon that may be holding the stale entries for a few
extra (seconds/minutes)....

	-- Cheers
	-- James

On Tue, 17 Oct 2000, Mark C Smith wrote:

> There is no such behavior built into Netscape Directory Server, and I do
> not know of any bugs like this in the server.  Maybe you are doing some
> caching on the client side?  Or something else is going on.  Here is a
> good starting point for assistance with Netscape/iPlanet Directory
> Server:
> 
> http://www.iplanet.com/support
> 
> If you send me a small amount of sample code via private mail I will
> take a look also.
> 
> -- 
> Mark Smith
> Directory Product Development / iPlanet E-Commerce Solutions
> My words are my own, not my employer's.            Got LDAP?
> 
> 
> "Morris, Cavan" wrote:
> > 
> > This question may be a little bit off topic, but I've found this list to be
> > a useful source of information in the past so I thought I'd give it a try.
> > 
> > I'm writing some ldap clients using the Netscape Java SDK v4.1 against a
> > Netscape Directory Server.
> > 
> > The client adds entries, deletes entries and changes passwords for those
> > entries and I've run into some irregularities.
> > 
> > 1) If the password for an entry is changed you can still authenticate with
> > the old password until you authenticate with the new password.
> > 
> > 2) If you delete an entry you can still authenticate as that user one more
> > time.
> > 
> > Are these safety features so if you accidentally delete the administrator
> > you can go back in and recreate it?
> > 
> > Is there some sort of a commit I can do in order to make the changes take
> > effect immediately?
> > 
> > Any info would be helpful.
> > Thanks
> > -Cavan
>