Incommon SP and IDP

[Losen, Stephen C. (scl)]

Hi folks,

I've seen this error on some SPs when you browse the SP with "http" instead of "https" (and the SP does not redirect to https).  The URLs in the SP metadata are all "https" but if you browse with "http" then the SP puts a "http" URL in the login request, which does not match any "https" URL in the metadata.

Stephen C. Losen
ITS - Systems and Storage
University of Virginia
scl at virginia.edu    434-924-0640


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of privas
Sent: Monday, February 20, 2017 6:04 PM
To: users at shibboleth.net
Subject: Incommon SP and IDP

Hello all,

I'm trying to get my IDP to communicate with our modolabs SP who registered
their app with InCommon. When I try to login, I'm prompted to an error page
which says: "The login service was unable to identify a compatible way to
respond to the requested application. This is generally to due to a
misconfiguration on the part of the application and should be reported to
the application's support team or owner." Looking at a previous post, Scott
mentions that "The error means the SP requested use of a response location
not authorized by the metadata." From the past couple of SSO projects I've
implemented, I would use a SAML tracer to debug but I don't see any traces
at all. Could their endpoint be wrong? Any help would be greatly appreciated
as each SSO project is a learning experience!!!



--
View this message in context: http://shibboleth.1660669.n2.nabble.com/Incommon-SP-and-IDP-tp7631523.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.
-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net