MFA Error

[Nate Klingenstein]

Noriyuki,

The login process didn't result in a principal that could satisfy the
AuthnRequest.  Without a successfully authenticated user, the IdP has to
return an error to the SP.

You want to compare the AuthnContext requested in the AuthnRequest, SP
metadata, and relying party configuration to the AuthnContexts that
resulted from the MFA process.  There might have been no result from
authentication at all, or the resulting principal types might not match, so
they can't be used.

There will be something helpful in the logs.

I hope this helps,
Nate.

On Mon, May 14, 2018 at 4:18 PM, Noriyuki TAKEI <ntakei at sios.com> wrote:

> Hi,all
>
> I'm using MultiFactorAuthnConfiguration in Shibboleth 3.3.2.
>
> But error as below occurred when accessing the sp.
>
> <saml2p:Status>
>     <saml2p:StatusCode Value="urn:oasis:names:tc:
> SAML:2.0:status:Requester">
>         <saml2p:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:
> NoAuthnContext"/>
>     </saml2p:StatusCode>
>     <saml2p:StatusMessage>An error occurred.</saml2p:StatusMessage>
> </saml2p:Status>
>
> Does someone may give a hint?
>
>
>
>
> --
> For Consortium Member technical support, see https://wiki.shibboleth.net/
> confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180514/3d0946c9/attachment.html>