Last post Dec 20, 2017 05:51 PM by PatriceSc
Dec 20, 2017 05:36 PM|bobj181|LINK
We have an old Web Form App that we are trying to integrate a Ping Identity SSO Service. The implementation of this service is such that once authenticated on the SSO side, it makes a POST Call to the specific Web Page in the Web Form App.
I am seeing something strange, and can't tell if it is ASP.NET or IIS. I can see the Service making the POST Call in the IIS logs, but after some digging, when the web page that is defined for the SSO to POST to starts to load (I am doing the check on the
Page Init step) the Request Type from the Request object is set to Get and I have no keys it it. I am expecting a SAML Key to be returned.
This is what I see in the IIS Log:
2017-12-20 16:37:34 GET /mySSO/default.aspx - 80
2017-12-20 16:37:34 POST /mySSO/default.aspx Go=No 80
2017-12-20 16:37:35 GET /mySSO/default Go=No 80
In addition, it is stripping off the .aspx of the page a Get is made (don't know where that is coming from).
Any insight would be greatly appreciated.
Dec 20, 2017 05:51 PM|PatriceSc|LINK
The http status code and the referrer might help to better understand if you have a redirection and who is making that.
I would even likely use https://msdn.microsoft.com/en-us/library/system.web.httprequest.saveas(v=vs.110).aspx or
https://docs.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis to trace all requests and better understand the authentication flow.
/mySSO/default works or does it give a 404 error ?