<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi,</p>
    <p>the customer confirmed that the 1.1 version does work.</p>
    <p>Thanks Gernot and all,</p>
    <p>Martin<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 13.03.2018 09:40, Martin Haase
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:95f2a7e6-fb17-aca2-bf8e-22ca7d909512@DAASI.de">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <p>Hi Gernot,</p>
      seems like I fell into the SAML errata trap. I'l have a try and
      test urn:oasis:names:tc:SAML:<b>1.1</b>:nameid-format:unspecified.
      <br>
      <br>
      Cheers<br>
      Martin<br>
      <br>
      <br>
      <div class="moz-cite-prefix">On 13.03.2018 09:21, Gernot
        Hassenpflug wrote:<br>
      </div>
      <blockquote type="cite" cite="mid:yol37148jyc.fsf@asahi-net.or.jp">
        <pre wrap="">Martin Haase <a class="moz-txt-link-rfc2396E" href="mailto:Martin.Haase@DAASI.de" moz-do-not-send="true"><Martin.Haase@DAASI.de></a> writes:

</pre>
        <blockquote type="cite">
          <pre wrap="">Hi folks,

this IdP sends a <NameID> without a "Format" attribute. SAML specs say
that "if no Format value is provided, then the value
urn:oasis:names:tc:SAML:1.0:nameid-format:unspecified ... is in effect".
Thus I would expect to be able to write this in attribute-map.xml on the
SP side:

    <Attribute
name="urn:oasis:names:tc:SAML:1.0:nameid-format:unspecified" id="some_id">
        <AttributeDecoder xsi:type="NameIDAttributeDecoder"
formatter="$Name" />
    </Attribute>

...but it does not seem to return the NameID as an attribute. Leaving
aside interoperability, how must the SP be configured to accomodate a
SAML message from this particular IdP?
</pre>
        </blockquote>
        <pre wrap="">Hi Martin,
On our SP setup, as an example, we use:
<Attribute name="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified" id="unspecified-id">
     <AttributeDecoder xsi:type="NameIDAttributeDecoder" formatter="$Name" defaultQualifiers="true"/>
</Attribute>
(defaultQualifiers is not something we looked at here, just left in as
part of our defaults)

In settin up our SP, I noted that I had referenced this example (obviously after reading
the actual Shibboleth Wiki pages first):
<a class="moz-txt-link-freetext" href="https://stackoverflow.com/questions/44464929/shibboleth-service-provider-how-to-populate-remote-user-variable" moz-do-not-send="true">https://stackoverflow.com/questions/44464929/shibboleth-service-provider-how-to-populate-remote-user-variable</a>

Best regards,
Gernot Hassenpflug
</pre>
      </blockquote>
      <br>
      <pre class="moz-signature" cols="72">-- 
Dr. Martin Haase, Solutions Engineer

DAASI International GmbH        
Europaplatz 3                   
D-72072 Tübingen                
Germany                    

phone: +49 7071 407109-0
fax:   +49 7071 407109-9  
email: <a class="moz-txt-link-abbreviated" href="mailto:martin.haase@daasi.de" moz-do-not-send="true">martin.haase@daasi.de</a>
web:   <a class="moz-txt-link-abbreviated" href="http://www.daasi.de" moz-do-not-send="true">www.daasi.de</a>

Sitz der Gesellschaft: Tübingen
Registergericht: Amtsgericht Stuttgart, HRB 382175
Geschäftsleitung: Peter Gietz
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Dr. Martin Haase, Solutions Engineer

DAASI International GmbH        
Europaplatz 3                   
D-72072 Tübingen                
Germany                    

phone: +49 7071 407109-0
fax:   +49 7071 407109-9  
email: <a class="moz-txt-link-abbreviated" href="mailto:martin.haase@daasi.de">martin.haase@daasi.de</a>
web:   <a class="moz-txt-link-abbreviated" href="http://www.daasi.de">www.daasi.de</a>

Sitz der Gesellschaft: Tübingen
Registergericht: Amtsgericht Stuttgart, HRB 382175
Geschäftsleitung: Peter Gietz
</pre>
  </body>
</html>