[EMAIL PROTECTED] wrote:
Hi,
Hi Bob,
we performed some tests using an ActiveDirectory as LDAP authentication
backend for the repository.
Everything seems to work except for one thing.
- Suppose the root user takes a look at the user list in the CMS
dashboard
- Someone adds a new user to the ActiveDirectory and adds it to the
correct group, let's say Author
- this new user can log in and has the correct rights as an author
So far, so good ;)
- root user looks at the User dashboard in the CMS but still doesn't see
that user (even after a couple of hours)
I'm quite sure that if you login directly to the repository with a
browser, that you will see the new users. So it probably is a CMS issue.
- another user that never logged in before that will be able to see the
added user
- a restart of the CMS will rectify the situation
I suppose that the user list is cached somehow and this for a very long
time?
It looks like the CMS caches the user list. The repository will cache it
only for a few minutes by default.
I guess the repository doesn't (and cannot) send a JMS message to
invalidate the cache to the CMS. The repository does send a message when
the users are stored in the repository itself.
Does any CMS expert know if it is possible to force invalidation of the
users list after a while (like an hour) even though event caching is used?
Regards,
Bart
I tried this with repository 1.2.13 and the cms 6.05.02 binary
thanks
Bob
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
--
Hippo
Oosteinde 11
1017WT Amsterdam
The Netherlands
Tel +31 (0)20 5224466
-------------------------------------------------------------
[EMAIL PROTECTED] / http://www.hippo.nl
--------------------------------------------------------------
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
