SP not receiving attributes from our IdP

[Tom Scavo]

On Thu, Sep 15, 2016 at 8:23 PM, Gould, Samuel <Samuel.Gould at sdstate.edu> wrote:
>
>   - We just recently spun up the Shib v3 IdP, and gave it a different
> hostname

That's all right as long as you don't share metadata with the new hostname.

>     than the Shib v2 IdP; the entity IDs are the same

+1

>   - Within a short time frame, we need to establish SSO with a specific SP

Separate this from the V3 migration. Don't mix the two. This is why
you're having problems.

>   - Both our organization and this SP are members of the InCommon federation

Which means they already have your metadata. Don't change your
metadata, full stop.

>   - Currently, InCommon has our v2 endpoints listed
>
>   - We do not have time to push our new v3 endpoints to InCommon before this
> SP

Don't change your endpoints, at least not until the V3 migration is
complete. See "Upgrading to Shibboleth IdP V3" in the spaces wiki:
https://spaces.internet2.edu/x/GYtHBQ

>   - Even if we gave the SP standalone metadata for our v3 IdP (instead of
> going
>
>     through InCommon), our v3 IdP is not well tested enough for management
> to
>
>     feel comfortable enough to use it within our short timeframe

Do not change your metadata.

Tom