question about IdP v2 upgrade and REMOTE_USER variable

[Nate Klingenstein]

Mike,

There’s not enough information in here for us to really tell you.  You’ll need to check the outbound assertion/attributes and the attributes that are included in them and the attribute mapping by the SP.  It’s highly probable that you missed something in your configuration translation.

Check whether release rules changed, that you don’t have a needed NameID mapping, whether you’re releasing attributes with a different name, and so forth.

Your IdP will log attributes going out, and the SP will log attributes inbound, including those it drops for mapping or policy reasons.

Hope this helps,
Nate.

> On Jun 13, 2016, at 12:16, Michael Weyandt <maw120 at zips.uakron.edu> wrote:
> 
> Hello fellow shib users,
> 
> I’m in the middle of an IdP upgrade and am running into an issue I haven’t been able to make much progress on.
> 
> When authenticating with my v3 instance my SPs are not getting the REMOTE_USER variable set correctly, but does when using my v2 instance.
> They are, to my knowledge, setup identically but with the updated configuration.
> 
> We are using kerberos as the authentication back-end.
> 
> Is there anything different between v2 and v3 that I am overlooking pertaining to this, or does this have nothing to do with shibboleth?
> 
> Thanks,
> Mike Weyandt
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net