configuring idp to release the "remote_user" as nameid

[David Mansfield]

On 06/25/2013 10:48 AM, Peter Schober wrote:
> * David Mansfield <shibboleth at dm.cobite.com> [2013-06-25 16:38]:
>> I had already tried the below in attribute-resolver.xml (and released it
>> it attribute-filter.xml):
>>
>> <resolver:AttributeDefinition xsi:type="PrincipalName"
>> xmlns="urn:mace:shibboleth:2.0:resolver:ad"
>>                                 id="persistentId" />
>>
>>
>> and it isn't working for me.  Now there is no nameid at all in the
>> assertion.  Does this have to have any AttributeEncoders or should it be
>> embedded in another element?
> It needs an encoder in order to produce anything on the wire, yes.
> Look at the "eduPersonTargetedID" example in the resolver config if
> you're hell-bent on violating the SAML spec (cf my other mails),
>
Well, you definitely make a very good case for changing my ways ;-).  My 
only other experience with SAML is running a Shibboleth SP where the 
partner is sending the kerberos principal as a 
urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified, so I thought this 
was standard practice.

I'll look into a computedId solution, and send the kerberos principal as 
a regular attribute.  On the SP side I can map this using the attribute 
map however I want anyway.

Thanks,
David