Open borabilgin opened 8 years ago
Take a look at https://github.com/elerch/SAML2/pull/11 and let me know if it solves the issue for you. There's some evaluation I still want to make before accepting it, but you seem to have the issue @zarusz is solving.
Exactly the issue I'm having. This fixes my problem. Thanks @zarusz! On Mar 11, 2016 6:03 PM, "Emil Lerch" notifications@github.com wrote:
Take a look at #11 https://github.com/elerch/SAML2/pull/11 and let me know if it solves the issue for you. There's some evaluation I still want to make before accepting it, but you seem to have the issue @zarusz https://github.com/zarusz is solving.
— Reply to this email directly or view it on GitHub https://github.com/elerch/SAML2/issues/10#issuecomment-195595954.
When testing SAML2 responses, this is what I do to decode the response string: 1- URL decode 2- Base64 decode 3- Inflate the string
With this method, I'm able to see SAML2 responses. Many online SAML2 debugging tools provide this as well.
However, this library only URL decodes and then Base64 decodes, and does not inflate the string - hence cannot understand the response (the relevant code is in Utility.cs, GetDecodedSamlResponse method)
Am I missing something - is this not part of the standard?