<div dir="ltr"><div><div><div>Hi, <br><br></div>I&#39;m trying to integrate keycloak into a the french research federation of identity (renater) and I&#39;m facing some problems.<br></div>Actually, when IdP respond to keycloak i&#39;m getting the following error : <br>PL00084: Writer: Unsupported Attribute Value:org.keycloak.dom.saml.v2.assertion.NameIDType<br><br></div><div>It seems that this IdP is using transient NameID policy only and using the unspecified field in the idp config in keycloak generate this exception as a return.<br><br></div><div>Log of the keycloak server is joined.<br><br></div><div>I have no idea of what happening because when I was using the test federation, everything was working but no I&#39;m in the production federation, login fails.<br><br></div><div>The renater federation is using Shibolleth and keycloak is not supported by federation moderators so I&#39;m alone in the dark now...<br><br></div><div>Renater provides an IdP list that I have to parse and synchronized with IdP in keycloak. As a return I provide a list of all endpoints for each keycloak registered IdP to allow federation IdP to answear correctly to the right endpoint. All of this is done by a small web app deployed aside keycloak and using REST API to synchronize all the IdP.<br><br></div><div>One of the IdP entity descriptor is joined. As you can see, only transient nameid policy is supported and if I configure keycloak to use email or persistent, I received a response saying that the nameid is not supported : <br><br>&lt;samlp:AuthnRequest xmlns:samlp=&quot;urn:oasis:names:tc:SAML:2.0:protocol&quot; xmlns=&quot;urn:oasis:names:tc:SAML:2.0:assertion&quot; AssertionConsumerServiceURL=&quot;<a href="https://demo-auth.ortolang.fr/auth/realms/ortolang/broker/2db5eab3f83cbaa5a322dcf3f9ac552d/endpoint">https://demo-auth.ortolang.fr/auth/realms/ortolang/broker/2db5eab3f83cbaa5a322dcf3f9ac552d/endpoint</a>&quot; Destination=&quot;<a href="https://janus.cnrs.fr/idp/profile/SAML2/POST/SSO">https://janus.cnrs.fr/idp/profile/SAML2/POST/SSO</a>&quot; ForceAuthn=&quot;false&quot; ID=&quot;ID_c53b5759-cb97-4e95-b540-877a7a6c625d&quot; IsPassive=&quot;false&quot; IssueInstant=&quot;2015-12-22T16:13:15.987Z&quot; ProtocolBinding=&quot;urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST&quot; Version=&quot;2.0&quot;&gt;&lt;saml:Issuer xmlns:saml=&quot;urn:oasis:names:tc:SAML:2.0:assertion&quot;&gt;<a href="https://demo-auth.ortolang.fr/auth/realms/ortolang">https://demo-auth.ortolang.fr/auth/realms/ortolang</a>&lt;/saml:Issuer&gt;&lt;samlp:NameIDPolicy AllowCreate=&quot;true&quot; Format=&quot;urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress&quot;/&gt;&lt;/samlp:AuthnRequest&gt;
<br><br>&lt;saml2p:Response xmlns:saml2p=&quot;urn:oasis:names:tc:SAML:2.0:protocol&quot; Destination=&quot;<a href="https://demo-auth.ortolang.fr/auth/realms/ortolang/broker/2db5eab3f83cbaa5a322dcf3f9ac552d/endpoint">https://demo-auth.ortolang.fr/auth/realms/ortolang/broker/2db5eab3f83cbaa5a322dcf3f9ac552d/endpoint</a>&quot; ID=&quot;_9d03761957aade819b6823c35bbab278&quot; InResponseTo=&quot;ID_c53b5759-cb97-4e95-b540-877a7a6c625d&quot; IssueInstant=&quot;2015-12-22T16:13:16.420Z&quot; Version=&quot;2.0&quot;&gt;&lt;saml2:Issuer xmlns:saml2=&quot;urn:oasis:names:tc:SAML:2.0:assertion&quot; Format=&quot;urn:oasis:names:tc:SAML:2.0:nameid-format:entity&quot;&gt;<a href="https://janus.cnrs.fr/idp">https://janus.cnrs.fr/idp</a>&lt;/saml2:Issuer&gt;&lt;saml2p:Status&gt;&lt;saml2p:StatusCode Value=&quot;urn:oasis:names:tc:SAML:2.0:status:Responder&quot;&gt;&lt;saml2p:StatusCode Value=&quot;urn:oasis:names:tc:SAML:2.0:status:InvalidNameIDPolicy&quot;/&gt;&lt;/saml2p:StatusCode&gt;&lt;saml2p:StatusMessage&gt;Required NameID format not supported&lt;/saml2p:StatusMessage&gt;&lt;/saml2p:Status&gt;&lt;/saml2p:Response&gt;
<br></div><div><br><br></div><div>Any help would be gracefully appreciated.<br><br></div><div>Thanks a lot, Jérôme.<br></div><div><br></div></div>