New Shibboleth daemon on new server - user/wayf page just reloads over and over

[Cantor, Scott]

On 9/16/13 3:05 PM, "Johnny Lasker" <jlasker at educause.edu> wrote:

>I'm following up on this post as I work with Ben. We made modifications to
>our config to 'modernize' it by swapping out SessionInitiator for SSO,
>using just logout, and generally consolidating, but had no luck in
>changing our outcome.

It seems like the outcome completely changed because you didn't actually
build a working config to test with yet.

>I've attached our current shibboleth2.xml file if anyone has any thoughts
>on what's off about it.

There's nothing obviously wrong, I can't think of any way for it to behave
that way.

> I also attached our 'modern' version. When we load
>try the modern version, we get a 500 error before reaching our WAYF page.

An obvious error I see in it is that <SSO WAYF="SAMLDS"...
is not valid, it's discoveryProtocol="SAMLDS", not WAYF="SAMLDS".

I don't recall seeing a log trace on DEBUG of both log files when this
happens.

-- Scott