I’ve been meaning to ask this for years, but does anyone know how to speed up the caching of changes to the person document (HTTPPassword) field? I’ve got a web app where people have to change their passwords after first login and it can take minutes before the change takes effect. Is there some magical server setting that affects this?
This problem has existed as long as the HTTP task has.
Any input would be GREATLY appreciated. It doesn’t take as long as it used to (I could swear it was overnight) but minutes is still unacceptable in the internet world.
Print "Starting refreshing views"
Dim s As New NotesSession, v As NotesView
Print "Refreshing " & "($Users)"
Set v=s.Currentdatabase.Getview("($Users)")
Call v.Refresh()
Print "Refreshing " & "($LDAPCN)"
Set v=s.Currentdatabase.Getview("($LDAPCN)")
Call v.Refresh()
Print "Refreshing " & "($ServerAccess)"
Set v=s.Currentdatabase.Getview("($ServerAccess)")
Call v.Refresh()
Print "Done refreshing views"
End Sub
Added user to deny access only group listed in server deny access field, ran agent:
tell amgr run names.nsf ‘Refresh Access Views’
12/01/2009 11:20:16 AM AMgr: Start executing agent ‘Refresh Access Views’ in ‘names.nsf’
12/01/2009 11:20:16 AM Agent Manager: Agent printing: Starting refreshing views
12/01/2009 11:20:16 AM Agent Manager: Agent printing: Refreshing ($Users)
12/01/2009 11:20:16 AM Agent Manager: Agent printing: Refreshing ($LDAPCN)
12/01/2009 11:20:16 AM Agent Manager: Agent printing: Refreshing ($ServerAccess)
12/01/2009 11:20:16 AM Agent Manager: Agent printing: Done refreshing views
12/01/2009 11:20:16 AM AMgr: Agent ‘Refresh Access Views’ in ‘names.nsf’ completed execution
Then I successfully logged on server using denied user credentials and read emails, wrote emails, logged of and logged on again.