> Making a universal login method would be difficult whether it is combined
> with authorization or not, since we want to support more then just simple
> username and password authentication. One way of doing it would be to use
> callback handlers just like jaas does.
> Another option is not defining a login method at all but let that be an
> implementation detail.
Exactly. There is no need to do it in Wicket at all! There's JAAS,
J2EE security, Acegi, etc that handles this well.
huh???
It is about integrating those into wicket. Not replacing them.
