[jboss-jira] [JBoss JIRA] (WFLY-3226) Add test cases to verify LDAP caching on security realms.

[Darran Lofthouse (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12962933#comment-12962933 ] 

Darran Lofthouse commented on WFLY-3226:
----------------------------------------

Hello [~friler] for the moment I would suggest a public comment on the issue to make sure others are aware you are looking into this.

FYI there is a pull request in the queue to add support for LDAP referrals, this does make some changes to the tests so your changes would need to be applied after that one.

Just one additional point, testing of actual timeouts is probably not going to be possible, those kind of tests tend to delay the overall build and also risk introducing race conditions and intermittent failures into the testsuite which is never popular ;-)
                
> 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