metadata-support - [Metadata-Support] InCommon IdPv3 Issue
Subject: InCommon metadata support
List archive
- From: "Kelly, Kyle E" <>
- To: "''" <>
- Subject: [Metadata-Support] InCommon IdPv3 Issue
- Date: Wed, 2 Mar 2016 14:09:38 +0000
- Accept-language: en-US
I upgraded from IdPv2 to IdPv3 this morning and I am having a problem with our Incommon Federation. We have seven SPs configured in our environment and six of them are working without issue. The 7th SP is Cayuse which authenticates
thru Incommon. I made sure not to change the EntityID or any of the endpoints and all of the SAML signing Keys have been migrated over from the previous server. There are no error messages on the page or in the logs. When we sign into cayuse, it just redirects
to the default Cayuse sign in page from the IdP sign in page. How do I determine what I have missed during the migration? How would I go about verifying the SAML Endpoints are indeed the same? Is this the correct list for this type of question? Kyle Kelly System Software Specialist Information Technology Services The University of South Dakota Vermillion, SD 57069 |
- [Metadata-Support] InCommon IdPv3 Issue, Kelly, Kyle E, 03/02/2016
- [Metadata-Support] RE: InCommon IdPv3 Issue, Cantor, Scott, 03/02/2016
- Re: [Metadata-Support] RE: InCommon IdPv3 Issue, Tom Scavo, 03/02/2016
- RE: [Metadata-Support] RE: InCommon IdPv3 Issue, Cantor, Scott, 03/02/2016
- Re: [Metadata-Support] RE: InCommon IdPv3 Issue, Tom Scavo, 03/02/2016
- RE: [Metadata-Support] RE: InCommon IdPv3 Issue, Cantor, Scott, 03/02/2016
- Re: [Metadata-Support] RE: InCommon IdPv3 Issue, Tom Scavo, 03/02/2016
- [Metadata-Support] InCommon IdPv3 Issue, Dan Schwartz, 03/02/2016
- Re: [Metadata-Support] InCommon IdPv3 Issue, Mike Flynn, 03/02/2016
- [Metadata-Support] RE: InCommon IdPv3 Issue, Cantor, Scott, 03/02/2016
Archive powered by MHonArc 2.6.16.