Unable to parse SAML attributes and redirecting the request back to the URL

[Cantor, Scott]

On 6/28/13 3:00 PM, "justin9" <justin9 at ymail.com> wrote:

>Hi Scott,
>
>well i also see cookies being generated in my computer.

Cookies come from web servers.

>i went trough the documentation and i believe but might be wrong that the
>error is happening at the step # 6  Back to the Protected Resource.

I believe your redirect either doesn't happen, or happens with no session
cookie, which is what causes all loops.

>I have the debug info from my shibd.log and it doesnt have any place where
>session is invalid.

No, because most likely no session cookie is being supplied by your
client, but you should check native.log as well.

That's a loop:

2013-06-28 11:36:41 INFO Shibboleth.SessionCache [1]: new session created:
ID (_c41a8cf8ea72f00ae2f9b755d32814f9) IdP
(https://abccompany.org/SAML2/IDP)
Protocol(urn:oasis:names:tc:SAML:2.0:protocol) Address (10.1.1.202)
2013-06-28 11:36:41 DEBUG Shibboleth.SSO.SAML2 [1]: ACS returning via
redirect to: https://myserver/roundup
2013-06-28 11:36:41 DEBUG Shibboleth.Listener [1]: dispatching message
(default/Login::run::SAML2SI)


If the session cookie were present, it wouldn't jump from sending you to
the resource to initiating a new session.

Your log doesn't suggest a problem with the ACS and resource vhosts not
matching, which is another source of looping. Both use a bogus "myserver"
unqualified hostname, which should make them part of a common cookie
domain.

So I have no suggestion. You have no alternative but to trace the traffic
and determine why the shibsession cookie is not being returned at the end.

I'm on vacation, so do not expect any further responses, there's nothing
new here I can tell you.

-- Scott