[undertow-dev] cached authenticated sessions

[Bill Burke]

class CachedAuthenticatedSessionHandler {
     private boolean isCacheable(final SecurityNotification notification) {
         return notification.isProgramatic() || 
"FORM".equals(notification.getMechanism());
     }


Any new AuthenticationMechanism that wants session cached auth is forced 
to specify "FORM" for its mechanism when calling 
authenticationComplete().  Is this a bad thing?

Should "cacheable" be a part of the authenticationComplete() callback 
instead?

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com