Add ability to verify Yubikey second factor, list second factors

Dep: https://github.com/SURFnet/Stepup-Middleware-clientbundle/pull/4

The identity ID is currently hard-coded to `45fb401a-22b6-4829-9495-08b9610c18d4`. This identity must be present in the middleware.

- [x] Translate translation keys
- [x] Change back to client@dev-develop
- [ ] Text message originator is the same for all text messages, make configurable and pass into service.
You may assume that the user is an identity, the firewall takes care of
that and there is no other notion of users. Either you are logged in with a
samltoken and an identity as user, or you're kicked out by the firewall.
There is nothing else. Hence no need to check that. You can be too
defensive,. That said I'm not going to fuss about it, it just doesn't add
anything.
On Dec 1, 2014 7:33 PM, "Reinier Kip" <notifications@github.com> wrote:

> In
> src/Surfnet/StepupSelfService/SelfServiceBundle/Controller/Controller.php:
>
> > +use Symfony\Component\Security\Core\SecurityContextInterface;
> > +
> > +class Controller extends FrameworkController
> > +{
> > +    /**
> > +     * @return Identity
> > +     * @throws AccessDeniedException When the registrant isn't registered using a SAML token.
> > +     */
> > +    protected function getIdentity()
> > +    {
> > +        /** @var SecurityContextInterface $tokenStorage */
> > +        $tokenStorage = $this->get('security.context');
> > +        $token = $tokenStorage->getToken();
> > +
> > +        if (!$token instanceof SamlToken) {
> > +            throw new AccessDeniedException('Registrant must be authenticated using a SAML token.');
>
> Then as a controller it is my concern that I'm indeed dealing with an
> Identity imo. I could remove the instanceof FooToken check, but the
> controller action won't work if the User is not an Identity.
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/SURFnet/Stepup-SelfService/pull/5/files#r21108297>.
>