{"action":"opened","issue":{"url":"https://api.github.com/repos/KentorIT/authservices/issues/518","repository_url":"https://api.github.com/repos/KentorIT/authservices","labels_url":"https://api.github.com/repos/KentorIT/authservices/issues/518/labels{/name}","comments_url":"https://api.github.com/repos/KentorIT/authservices/issues/518/comments","events_url":"https://api.github.com/repos/KentorIT/authservices/issues/518/events","html_url":"https://github.com/KentorIT/authservices/issues/518","id":163267663,"number":518,"title":"unexpected InResponseTo, No RelayState was detected issue","user":{"login":"jaydinslage","id":12753841,"avatar_url":"https://avatars.githubusercontent.com/u/12753841?v=3","gravatar_id":"","url":"https://api.github.com/users/jaydinslage","html_url":"https://github.com/jaydinslage","followers_url":"https://api.github.com/users/jaydinslage/followers","following_url":"https://api.github.com/users/jaydinslage/following{/other_user}","gists_url":"https://api.github.com/users/jaydinslage/gists{/gist_id}","starred_url":"https://api.github.com/users/jaydinslage/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jaydinslage/subscriptions","organizations_url":"https://api.github.com/users/jaydinslage/orgs","repos_url":"https://api.github.com/users/jaydinslage/repos","events_url":"https://api.github.com/users/jaydinslage/events{/privacy}","received_events_url":"https://api.github.com/users/jaydinslage/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-06-30T21:09:22Z","updated_at":"2016-06-30T21:09:22Z","closed_at":null,"body":"I've been researching this issue for quite some time now and want to get your take on it:\r\n\r\nOn our production servers, we get the following error:\r\n`Kentor.AuthServices.Exceptions.Saml2ResponseFailedValidationException: Received message contains unexpected InResponseTo \"idd8d95374ce064adcbcc578ea350fbc14\". No RelayState was detected so message was not expected to have an InResponseTo attribute`\r\n\r\nThe issue, obviously, is that the Kentor cookie is not in the HTTP POST. Well, it should be, lol. I am unable to reproduce this issue on our local machines and we receive quite a few every day.\r\n\r\n What I do know is that the \"Set-Cookie\" header **is** being set on the 303 redirect (the Kentor cookie). It does not, however, come back when the user has authenticated with the external system and they post to us (the HTTP POST to the Acs endpoint). This has happened on all browsers (Firefox, Chrome, and IE).\r\n\r\nThe post contains a valid SAMLResponse. In fact, the response the send looks perfect, except that the cookie is not there. I cannot determine any thing that is weird or wonky with the outgoing request that might be what is causing the issue.\r\n\r\nAny ideas, I'm at a loss.\r\n\r\n"}}
{"actor":{"display_login":"jaydinslage"}}