ErkanaAuth: Configuration Mechanics

[eluser]Michael Wales[/eluser]
I'm fielding a discussion on how (or, even if) ErkanaAuth should allow a more lenient approach to authentication. Currently, ErkanaAuth is very strict in its requirements (an accounts controller, an account table, passing of the identifying factor to multiple methods).

Head over to the Bitbucket Issue and join in on the conversation - I'm looking for some out of the box thinking that promotes the ideas that have always been behind Erkana (easy to use, non-invasive - an enabler to authentication).