IdP v2 to v3 migration success story

[Cantor, Scott]

On 7/1/15, 9:51 AM, "users on behalf of Paul Engle" <users-bounces at shibboleth.net on behalf of pengle at rice.edu> wrote:


>
>  I just wanted to share that we cut over our production IdP to the new
>3.1.1 servers yesterday, and everything went very smoothly. Much thanks
>to Scott, Marvin, & the rest of the team for the great documentation and
>all the hard work on the new version.

You're welcome.

>The only small gotcha I experienced was one of my own making. In v2, I
>relied on the metadata I manually crafted for a relying party to
>determine the NameIDFormat precedence. It was one of the first of those
>I had to deal with, and I'm sure I didn't know exactly what I was doing.
>In any event, after the upgrade, since there were multiple NameIDFormats
>listed, the v3 IdP started sending a transient id instead of the custom
>id I was generating. Once I overrode the nameIDFormatPrecedence property
>in the relying party bean, all was well. In retrospect, I probably could
>have just removed all the other NameIDFormats from the metadata, but
>this worked, so I'm going with it for now.

Hmm, I'll have to look but my recollection was that it should still be ordered. I certainly didn't intend to change anything about the selection behavior when it comes to metadata. It might not be a fixable bug, but it sounds like a bug anyway.

I also deeply apologize for the fact that 3.1.2 is going to be announced today, but we were waiting for you to finish, have to time these things perfectly.

-- Scott