<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Shibboleth only supports transient name ids?  I find that hard to
    believe.  Remember Keycloak would just look like any other client. 
    IMO you should go that route.<br>
    <br>
    Also though,  I think you might be able to write a Broker Mapper,
    take a look at UsernameTemplateMapper.  This SPI is undocumented and
    unsupported at the moment, but I hope to change that soon.<br>
    <br>
    <div class="moz-cite-prefix">On 1/14/2016 6:20 AM, Jérôme Blanchard
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAPNq5vYUHr54whQE0ivje+r-vA15Fmue0AsQcqcEso-_QSQ7dg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>Hi all, <br>
                    <br>
                  </div>
                  According to shibboleth specification, IdP of a
                  federation usually use transient NameID which makes
                  Shibboleth impossible to interface with keycloak, even
                  if we manage the Discovery Service externally in order
                  to maintain IdP list mapping between federation and
                  keycloak.<br>
                </div>
                It's really annoying for me and I'm trying to
                investigate a way to solve this problem.<br>
              </div>
              In my federation, some doc say that if you need to manage
              personnal user information in your application, you have
              to rely on a dedicated attribute in order to retreive real
              user id and not the transient opaque one. In this case, an
              attribute called eduPersoneTargetedId exists and can be
              use by shibboleth. <br>
            </div>
            I am trying to patch the saml broker in order to take into
            consideration this attribute in a kind of
            attributeToNameIdMapper but I have to admit that I'm lost a
            bit in the code.<br>
          </div>
          Do you think this approach is good ?<br>
          <br>
        </div>
        <div>Best regards, Jérôme.<br>
        </div>
        <br>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr">Le mer. 6 janv. 2016 à 09:31, Jérôme Blanchard
          &lt;<a moz-do-not-send="true" href="mailto:jayblanc@gmail.com">jayblanc@gmail.com</a>&gt;
          a écrit :<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div dir="ltr">
            <div>
              <div>
                <div>Hi Bill, all, <br>
                  <br>
                </div>
                In the case of a transient only nameid, would it be
                possible to create a dedicated attribute mapper in order
                to use for exemple the email attribute as name
                identifier ?<br>
                <br>
              </div>
              PS : the urn:mace:shibboleth:1.0:nameIdentifier is in fact
              use in SAML v1 for request a nameid that is transient
              also... so there is no solution in this way.<br>
              <br>
            </div>
            Best regards, Jérôme.<br>
          </div>
          <br>
          <div class="gmail_quote">
            <div dir="ltr">Le mar. 5 janv. 2016 à 16:13, Bill Burke &lt;<a
                moz-do-not-send="true" href="mailto:bburke@redhat.com"
                target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:bburke@redhat.com">bburke@redhat.com</a></a>&gt; a écrit :<br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">We won't
              be able to support temporary ids (transient) for awhile as
              it<br>
              requires temporary user creation which requires some
              rearchitecting.<br>
              <br>
              As for "urn:mace:shibboleth:1.0:nameIdentifier" if you
              spec it out in a<br>
              JIRA and it is simple enough to implement support for, we
              may be able to<br>
              get it in.<br>
              <br>
              On 1/5/2016 8:18 AM, Jérôme Blanchard wrote:<br>
              &gt; Hi Bill,<br>
              &gt;<br>
              &gt; Thanks for your answer regarding transient and
              temporary ids. I<br>
              &gt; understand the problem due to keycloak account
              creation and binding to<br>
              &gt; the IdP.<br>
              &gt; Renarter is using Shibboleth ; Is there is any work
              on shibboleth<br>
              &gt; integration for keycloak ?<br>
              &gt; If I look into the idps entities descriptors of
              renater, I found that it<br>
              &gt; uses also another nameid format based on shibboleth
              namesapce :<br>
              &gt;
&lt;md:NameIDFormat&gt;urn:mace:shibboleth:1.0:nameIdentifier&lt;/md:NameIDFormat&gt;<br>
              &gt;
&lt;md:NameIDFormat&gt;urn:oasis:names:tc:SAML:2.0:nameid-format:transient&lt;/md:NameIDFormat&gt;<br>
              &gt;<br>
              &gt; Do you think it is possible to patch the saml idp
              provider (or to create<br>
              &gt; another one dedicated to shibboleth) in order to
              integrate keycloak to<br>
              &gt; our identity federation (renater) ?<br>
              &gt;<br>
              &gt; Best whiches for this upcoming year and thanks for
              your great work<br>
              &gt; around keycloak.<br>
              &gt;<br>
              &gt; Jérôme.<br>
              &gt;<br>
              &gt;<br>
              &gt; Le mar. 22 déc. 2015 à 21:10, Bill Burke &lt;<a
                moz-do-not-send="true" href="mailto:bburke@redhat.com"
                target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:bburke@redhat.com">bburke@redhat.com</a></a><br>
              &gt; &lt;mailto:<a moz-do-not-send="true"
                href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>&gt;&gt;
              a écrit :<br>
              &gt;<br>
              &gt;     Our brokering doesn't support temporary user ids
              from the "parent" IDP.<br>
              &gt;        Transient Ids in SAML or temporary ids.<br>
              &gt;<br>
              &gt;     On 12/22/2015 11:46 AM, Jérôme Blanchard wrote:<br>
              &gt;      &gt; Hi,<br>
              &gt;      &gt;<br>
              &gt;      &gt; I'm trying to integrate keycloak into a the
              french research<br>
              &gt;     federation<br>
              &gt;      &gt; of identity (renater) and I'm facing some
              problems.<br>
              &gt;      &gt; Actually, when IdP respond to keycloak i'm
              getting the following<br>
              &gt;     error :<br>
              &gt;      &gt; PL00084: Writer: Unsupported Attribute<br>
              &gt;      &gt;
              Value:org.keycloak.dom.saml.v2.assertion.NameIDType<br>
              &gt;      &gt;<br>
              &gt;      &gt; It seems that this IdP is using transient
              NameID policy only and<br>
              &gt;     using<br>
              &gt;      &gt; the unspecified field in the idp config in
              keycloak generate this<br>
              &gt;      &gt; exception as a return.<br>
              &gt;      &gt;<br>
              &gt;      &gt; Log of the keycloak server is joined.<br>
              &gt;      &gt;<br>
              &gt;      &gt; I have no idea of what happening because
              when I was using the test<br>
              &gt;      &gt; federation, everything was working but no
              I'm in the production<br>
              &gt;      &gt; federation, login fails.<br>
              &gt;      &gt;<br>
              &gt;      &gt; The renater federation is using Shibolleth
              and keycloak is not<br>
              &gt;     supported<br>
              &gt;      &gt; by federation moderators so I'm alone in
              the dark now...<br>
              &gt;      &gt;<br>
              &gt;      &gt; Renater provides an IdP list that I have to
              parse and<br>
              &gt;     synchronized with<br>
              &gt;      &gt; IdP in keycloak. As a return I provide a
              list of all endpoints<br>
              &gt;     for each<br>
              &gt;      &gt; keycloak registered IdP to allow federation
              IdP to answear<br>
              &gt;     correctly to<br>
              &gt;      &gt; the right endpoint. All of this is done by
              a small web app deployed<br>
              &gt;      &gt; aside keycloak and using REST API to
              synchronize all the IdP.<br>
              &gt;      &gt;<br>
              &gt;      &gt; One of the IdP entity descriptor is joined.
              As you can see, only<br>
              &gt;      &gt; transient nameid policy is supported and if
              I configure keycloak<br>
              &gt;     to use<br>
              &gt;      &gt; email or persistent, I received a response
              saying that the nameid<br>
              &gt;     is not<br>
              &gt;      &gt; supported :<br>
              &gt;      &gt;<br>
              &gt;      &gt; &lt;samlp:AuthnRequest<br>
              &gt;   
               xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"<br>
              &gt;      &gt;
              xmlns="urn:oasis:names:tc:SAML:2.0:assertion"<br>
              &gt;      &gt;<br>
              &gt;     AssertionConsumerServiceURL="<a
                moz-do-not-send="true"
href="https://demo-auth.ortolang.fr/auth/realms/ortolang/broker/2db5eab3f83cbaa5a322dcf3f9ac552d/endpoint"
                rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="https://demo-auth.ortolang.fr/auth/realms/ortolang/broker/2db5eab3f83cbaa5a322dcf3f9ac552d/endpoint">https://demo-auth.ortolang.fr/auth/realms/ortolang/broker/2db5eab3f83cbaa5a322dcf3f9ac552d/endpoint</a></a>"<br>
              &gt;      &gt; Destination="<a moz-do-not-send="true"
                href="https://janus.cnrs.fr/idp/profile/SAML2/POST/SSO"
                rel="noreferrer" target="_blank">https://janus.cnrs.fr/idp/profile/SAML2/POST/SSO</a>"<br>
              &gt;      &gt; ForceAuthn="false"
              ID="ID_c53b5759-cb97-4e95-b540-877a7a6c625d"<br>
              &gt;      &gt; IsPassive="false"
              IssueInstant="2015-12-22T16:13:15.987Z"<br>
              &gt;      &gt;
              ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"<br>
              &gt;      &gt; Version="2.0"&gt;&lt;saml:Issuer<br>
              &gt;      &gt;<br>
              &gt;   
               xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"&gt;<a
                moz-do-not-send="true"
                href="https://demo-auth.ortolang.fr/auth/realms/ortolang"
                rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="https://demo-auth.ortolang.fr/auth/realms/ortolang">https://demo-auth.ortolang.fr/auth/realms/ortolang</a></a>&lt;/saml:Issuer&gt;&lt;samlp:NameIDPolicy<br>
              &gt;      &gt; AllowCreate="true"<br>
              &gt;      &gt;<br>
              &gt;   
 Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress"/&gt;&lt;/samlp:AuthnRequest&gt;<br>
              &gt;      &gt;<br>
              &gt;      &gt;<br>
              &gt;      &gt; &lt;saml2p:Response
              xmlns:saml2p="urn:oasis:names:tc:SAML:2.0:protocol"<br>
              &gt;      &gt;<br>
              &gt;     Destination="<a moz-do-not-send="true"
href="https://demo-auth.ortolang.fr/auth/realms/ortolang/broker/2db5eab3f83cbaa5a322dcf3f9ac552d/endpoint"
                rel="noreferrer" target="_blank">https://demo-auth.ortolang.fr/auth/realms/ortolang/broker/2db5eab3f83cbaa5a322dcf3f9ac552d/endpoint</a>"<br>
              &gt;      &gt; ID="_9d03761957aade819b6823c35bbab278"<br>
              &gt;      &gt;
              InResponseTo="ID_c53b5759-cb97-4e95-b540-877a7a6c625d"<br>
              &gt;      &gt; IssueInstant="2015-12-22T16:13:16.420Z"
              Version="2.0"&gt;&lt;saml2:Issuer<br>
              &gt;      &gt;
              xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion"<br>
              &gt;      &gt;<br>
              &gt;   
               Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity"&gt;<a
                moz-do-not-send="true" href="https://janus.cnrs.fr/idp"
                rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="https://janus.cnrs.fr/idp">https://janus.cnrs.fr/idp</a></a>&lt;/saml2:Issuer&gt;&lt;saml2p:Status&gt;&lt;saml2p:StatusCode<br>
              &gt;      &gt;<br>
              &gt;   
 Value="urn:oasis:names:tc:SAML:2.0:status:Responder"&gt;&lt;saml2p:StatusCode<br>
              &gt;      &gt;<br>
              &gt;   
 Value="urn:oasis:names:tc:SAML:2.0:status:InvalidNameIDPolicy"/&gt;&lt;/saml2p:StatusCode&gt;&lt;saml2p:StatusMessage&gt;Required<br>
              &gt;      &gt; NameID format not<br>
              &gt;      &gt;
supported&lt;/saml2p:StatusMessage&gt;&lt;/saml2p:Status&gt;&lt;/saml2p:Response&gt;<br>
              &gt;      &gt;<br>
              &gt;      &gt;<br>
              &gt;      &gt; Any help would be gracefully appreciated.<br>
              &gt;      &gt;<br>
              &gt;      &gt; Thanks a lot, Jérôme.<br>
              &gt;      &gt;<br>
              &gt;      &gt;<br>
              &gt;      &gt;<br>
              &gt;      &gt;
              _______________________________________________<br>
              &gt;      &gt; keycloak-user mailing list<br>
              &gt;      &gt; <a moz-do-not-send="true"
                href="mailto:keycloak-user@lists.jboss.org"
                target="_blank">keycloak-user@lists.jboss.org</a>
              &lt;mailto:<a moz-do-not-send="true"
                href="mailto:keycloak-user@lists.jboss.org"
                target="_blank">keycloak-user@lists.jboss.org</a>&gt;<br>
              &gt;      &gt; <a moz-do-not-send="true"
                href="https://lists.jboss.org/mailman/listinfo/keycloak-user"
                rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
              &gt;      &gt;<br>
              &gt;<br>
              &gt;     --<br>
              &gt;     Bill Burke<br>
              &gt;     JBoss, a division of Red Hat<br>
              &gt;     <a moz-do-not-send="true"
                href="http://bill.burkecentral.com" rel="noreferrer"
                target="_blank">http://bill.burkecentral.com</a><br>
              &gt;     _______________________________________________<br>
              &gt;     keycloak-user mailing list<br>
              &gt;     <a moz-do-not-send="true"
                href="mailto:keycloak-user@lists.jboss.org"
                target="_blank">keycloak-user@lists.jboss.org</a>
              &lt;mailto:<a moz-do-not-send="true"
                href="mailto:keycloak-user@lists.jboss.org"
                target="_blank">keycloak-user@lists.jboss.org</a>&gt;<br>
              &gt;     <a moz-do-not-send="true"
                href="https://lists.jboss.org/mailman/listinfo/keycloak-user"
                rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
              &gt;<br>
              <br>
              --<br>
              Bill Burke<br>
              JBoss, a division of Red Hat<br>
              <a moz-do-not-send="true"
                href="http://bill.burkecentral.com" rel="noreferrer"
                target="_blank">http://bill.burkecentral.com</a><br>
            </blockquote>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Bill Burke
JBoss, a division of Red Hat
<a class="moz-txt-link-freetext" href="http://bill.burkecentral.com">http://bill.burkecentral.com</a></pre>
  </body>
</html>