<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.hljs-name
{mso-style-name:hljs-name;}
.MsoChpDefault
{mso-style-type:export-only;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=FR link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Since we have migrated from 4.0.1 to 4.1.7 shibboleth version we have a strange behaviour when we connect with x509 certificate (using X509Internal through an MFA flow).<o:p></o:p></p><p class=MsoNormal>The authentication works well and users can connect with this factor but we see in the samlresponse that the <span class=hljs-name>AuthnContextClassRef is always « urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport ».<o:p></o:p></span></p><p class=MsoNormal><span class=hljs-name>In the idp logs we see now « password » instead of « </span>urn:oasis:names:tc:SAML:2.0:ac:classes:X509 ».<span class=hljs-name><o:p></o:p></span></p><p class=MsoNormal><span class=hljs-name>I don’t understand why the IDP sends such samlresponse although the sp doesn’t ask for this authentication factor (no authnContextClassRef required in the samlrequest) and our IDP uses the saml2.sso « classic » profile and has no defaultAuthenticationMethods configured.<o:p></o:p></span></p><p class=MsoNormal><span class=hljs-name>I tried with 4.2.1 and have the same behaviour.<o:p></o:p></span></p><p class=MsoNormal><span class=hljs-name>So could you tell me if this behaviour can be caused by some idp parameters (that i forgot or don’t know) or if it can be a « bug » with versions > 4.1.<o:p></o:p></span></p><p class=MsoNormal><span class=hljs-name><o:p> </o:p></span></p><p class=MsoNormal><span class=hljs-name>Thanks.<o:p></o:p></span></p><p class=MsoNormal><span class=hljs-name>nico</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>