Hi,
This issue has been fixed (atleast for us) using the Caching policies. WE had a
DefaultCacheTimeOut of "0" which meant the authenticate() was called everytime
in the following piece of code. of the authentication.
The latency that was a problem for us in our design was the authenticate() that
created DefaultLoginConfig using reflection. A few milliseconds extra but on a
real time server , it was a major impact for us.
Thanks
Bala
| Code snippet from the Jboss source code (JaasSecurityManager)
|
| public boolean isValid(Principal principal, Object credential,
|
| Subject activeSubject)
|
| {
|
| // Check the cache first
|
| DomainInfo cacheInfo = getCacheInfo(principal, true);
|
| if( trace )
|
| log.trace("Begin isValid, principal:"+principal+", cache info:
"+cacheInfo);
|
|
|
| boolean isValid = false;
|
| if( cacheInfo != null )
|
| {
|
| isValid = validateCache(cacheInfo, credential, activeSubject);
|
| if( cacheInfo != null )
|
| cacheInfo.release();
|
| }
|
| if( isValid == false )
|
| isValid = authenticate(principal, credential, activeSubject);
|
| if( trace )
|
| log.trace("End isValid, "+isValid);
|
| return isValid;
|
| }
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167786#4167786
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167786
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
