Upgrading old v2 IdP, lots of deprecated/unsupported messages

Cantor, Scott cantor.2 at osu.edu
Thu Apr 28 16:52:55 EDT 2016

On 4/28/16, 4:37 PM, "users on behalf of Ian Bobbitt" <users-bounces at shibboleth.net on behalf of ibobbitt at grnoc.iu.edu> wrote:

>I'm working on upgrading a rather old v2 IdP to the latest v3, and I'm getting a lot of deprecated and unsupported log messages.

Most of them are just identifying things in the legacy relying-party file that are dead or have been superseded, or a few things in the resolver that also can just be deleted.

The types of metadata sources being used are clear signals you need to clean them up, because it's relying on legacy code. Things that are being ignored in the file are, well, ignored, you can remove them.

The overall move to the updated relying-party format is a good idea but doesn't have to be rushed.

>Should I spend time cleaning this up, or will I be better served starting from a fresh v3 IdP install with the same Entity ID and key/cert? I do have this upgraded test IdP working, but the warnings are worrying and will add to confusion later.

You won't fix most of them by starting over. If you started to create a resolver file from scratch, you'd be ending up with the file you have now and removing the stuff that's dead, so there's not much point in starting over to end up having to do the same things.

If it's working, then you can clean up the warnings at your convenience.

-- Scott

More information about the users mailing list