servicenow SAML 2 integration

[Paul B. Henson]

> From: Paul B. Henson
> Sent: Wednesday, April 23, 2014 4:38 PM
>
> I've been asked to integrate our shibboleth idp with servicenow. I've seen a
> few postings regarding this, but would like to clarify a couple of issues.

Our campus is working with a consulting group called Cloud Sherpas to get our upcoming servicenow instance configured. I had complained to them about the lack of Incommon integration and kludginess, and also specifically about how they would handle a key rotation, given their manual metadata cut-and-paste process. They opened a ticket with ServiceNow for us, and they responded with this yesterday:

----------
2014-05-06 16:13:10 PDT - Aman Rao (NOW)
Solution proposed by Aman Rao (NOW)
 
How will the certificate rollover work with service now?
WP: InCommon Federation in MultiSSO will update the SAML configuration (including certificates) automatically per configured interval. By default once a day.
Is there a way to cleanly cut over, or will there be some period of breakage after the cutover while things are frantically manually reconfigured?
WP: Yes incommon federation in multisso will automatically manage the configuration / certificates that can also be manually updated if needed.
----------

There are absolutely no technical details, but they seem to be saying there's some way to integrate such that metadata is automatically pulled from the Federation, and a key rotation would happen transparently? I've seen nothing like this in any of the documentation I found, or in any of the responses I received about shibboleth integration with them from you guys. I'm thinking maybe they're just confused 8-/ and discussing something else they do?

I've asked for a clarification on this response, but I was just curious if anybody had heard of or had any idea what "Incommon Federation in MulitSSO" might be in relation with ServiceNow?

Thanks...