IdP v2 to v3 migration success story

[Paul Engle]

All,
  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.

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.

Otherwise, our implementation is fairly straightforward, so the
migration was pretty simple. I have personal bias against running things
in legacy mode, so I didn't do an upgrade that used old the old v2
format files. But even that was not much of a chore if you've dealt with
Spring before.

Now that we have v3 up and running, I plan to work on turning on some of
the new functionality like attribute release and CAS integration. For
now, I'm just going to bask in the glow of not having Terracotta to deal
with anymore. :)

  -paul

-- 
Paul D. Engle              |  Rice University
Systems Administrator III  |  Information Technology - MS119
(713)348-4702              |  PO Box 1892
pengle at rice.edu            |  Houston, TX 77252-1892