Authentiator and Identifier collection/registry upgrade. about authentication

[robertpustulka]

@burzum then for consistency we should add loadIdentifier() to the interface as well.

[robertpustulka]

I'm also having doubts about AuthenticationServiceInterface::loadAuthenticator(). Should authentication services be forced to implement this method? It is needed in default AuthenticationService but some implementations wouldn't need it, for example:

class SimpleService implements AuthenticationServiceInterface
{
    public function __construct(AuthenticateInterface $authenticator) {
        ...
    }
}

Another thing - is there a reason behind the interface being called AuthenticateInterface while all the authenticators use "authenticator" naming convention and reside under Authenticator namespace? (handled in #105)

[dereuromark]

@robertpustulka Sounds like the interface should get a rename here for consistency.

[robertpustulka]

Can we use core ObjectRegistry for collections? cakephp/core is required by this plugin anyway.

[burzum]

@robertpustulka can we close this as the PR's have been merged?

[robertpustulka]

@burzum There's only a matter of dropping AuthenticationServiceInterface::loadAuthenticator() on todo list. What do you think about it? Should we force this implementation? I think this method is only related to our approach in AuthenticationService. Someone just may want to implement simple service without any authenticators or configuration needed.

[burzum]

@robertpustulka if you need such a simple service, then you don't need that plugin at all. 😄