[
https://issues.jboss.org/browse/WFLY-3226?page=com.atlassian.jira.plugin....
]
Martin Choma edited comment on WFLY-3226 at 4/25/14 2:35 AM:
-------------------------------------------------------------
Hi,
I have solved the problem. In documentation there is missing initialization part. Now I
can proceed to writing tests.
I wonder is there any info regarding LDAP caching of security realms? In particular i am
interested when is record cached. When is record invalidated from cache?
Can you please describe closer your opinion of solution. Should I created new test suite,
let say LDAPCachingTestSuite or use some existing one. Should I register interceptor only
for Caching tests or can it be there for other tests as well.
Thanx,
Martin
was (Author: friler):
Hi,
I have solved the problem. In documentation there is missing initialization part. Now I
can proceed to writing tests.
I wonder is there any info regarding LDAP caching of security realms? In particular i am
interested when is record cached. When is record invalidated from cache?
Thanx,
Martin
Add test cases to verify LDAP caching on security realms.
---------------------------------------------------------
Key: WFLY-3226
URL:
https://issues.jboss.org/browse/WFLY-3226
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Domain Management, Test Suite
Reporter: Darran Lofthouse
Fix For: Awaiting Volunteers
The existing test cases are based on a statically defined set of LDIFs, testing of
caching could consider a couple of options: -
1 - Interceptors within ApacheDS to verify if calls hit the directory.
2 - Updates to the directory that would affect the outcome of tests if there is a cache
hit, tests can then be repeated with and without clearing the cache.
Note: It would be beneficial for this to use different users and groups and maybe even
different partitions so that test ordering does not affect the outcome if changes are made
to the directory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira