Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed issue with unrecognized bindings. Needed to work with SAMLTest.id #44

Merged
merged 2 commits into from
May 15, 2020

Conversation

dougwebb
Copy link
Contributor

SAMLTest.ID's metadata (https://samltest.id/saml/sp) includes a Shibboleth binding definition before the supported binding types. That was causing a "Binding not supported" exception to be thrown. My change ignores unsupported bindings, but will throw an exception if no supported bindings are found.

…t.ID's metadata (https://samltest.id/saml/sp) which includes a Shibboleth binding definition before the supported binding types.
Copy link
Owner

@i8beef i8beef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you'll probably have warnings about the if statements not using brackets. Can you add those real quick and Ill approve?

@dougwebb
Copy link
Contributor Author

No warnings about not using brackets; I use that syntax all of the time for one-liner validation/consistency checks. It's just a stylistic choice.

@i8beef
Copy link
Owner

i8beef commented May 15, 2020

Its a stylistic choice that is forbidden by StyleCop rules in this project though, and which you will see as warnings in the build, like so: https://ci.appveyor.com/project/i8beef/saml2/builds/32902619#L44

Thank you for fixing!

@i8beef i8beef merged commit 435d4df into i8beef:master May 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants