> > Formatting the digest into a string is another dimension that > > we would have to provide. The hash algorithm should be one login module > > option, and the representation of the digest another. This should include > > 'raw' for the raw digest byte[], 'base64' and 'hex'. > > > Won't the 'raw' option cause problems with the current interfaces which > all use Strings? > Yes, it would have to be returned as a String(byte[]).
> I was envisaging that it would just be an on or off "strict" flag in > AbstractSecurityProxy with "on" being b) and "off" being "c", with the > default being "on". If you're expected to provide your own proxy > implementation by subclassing this, then you would set the flag there, > and could provide more complex behaviour if you wanted. > > I don't see how you could configure the security proxy interceptor or > pass such information to the proxy without a lot of changes. And it > seems like excessive extra configuration information for such a small > difference. > Ok, I'll go with that. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
