<p>I'd like to thank you all for the help. The issue was just that, transientId was the needed format ti make it work.</p>
<p>I still don't quite understand how the google example is supposed to work given the fact that it uses unspecified and we're "not supposed to use that" but I am leaving it at that.</p>
<p>Thanks</p>
<div class="gmail_quote">On Jun 25, 2013 6:45 PM, "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 6/25/13 12:26 PM, "Byte Flinger" <<a href="mailto:byteflinger@gmail.com">byteflinger@gmail.com</a>> wrote:<br>
><br>
>If I understand correctly from the documentation, nameID definitions on<br>
>the SP or IDP metadata are just for info and don't really make a<br>
>difference is that correct?<br>
<br>
No. The wiki describes the NameID format selection process, and both of<br>
the metadata instances can impact that. Neither is strictly normative or<br>
impossible to ignore, but they can affect the outcome.<br>
<br>
>So basically what you guys are saying is that other than the use of<br>
>unspecified instead of transient or persistent, what I am doing is<br>
>correct?<br>
<br>
Pretty much.<br>
<br>
>Lastly, if one should not use unspecified then how does one get an<br>
>unspecified NameID like in the google example from the wiki, or is that<br>
>example just plain wrong?<br>
<br>
Google uses unspecified, that just doesn't happen to be sensible.<br>
<br>
-- Scott<br>
<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</blockquote></div>