Skip to content

Slo absence workaround #154

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

Merged
merged 2 commits into from
Apr 29, 2020
Merged

Slo absence workaround #154

merged 2 commits into from
Apr 29, 2020

Conversation

peppelinux
Copy link
Member

Using djangosaml2 with a Saml 2 Saml proxy like SATOSA I found an exception about the absence of SLO in the proxy features.

With this patch I can manage the exception raised by a faulty or absent SLO response.
I needed this to handle different IDP, some with SLO and some Not.

I made a single branch as usual, to make this feature very easy to be read as possible.

@peppelinux
Copy link
Member Author

Thank you for your revisions.
This patch solves problems coming from faulty idp's SLO implementations.
I need to use this with SATOSA wich do not have yet a SLO implementation.

Hope to see this merged soon @knaperek, with this commit my pplnx-dev branch and your master branch will be the same and I would use this latter in my project dependencies.

@peppelinux
Copy link
Member Author

@knaperek @OskarPersson could it be usefull for the next release?

@peppelinux
Copy link
Member Author

Still missing feedback from a long time, would there be the possibility to handle this?

@peppelinux peppelinux added this to the v0.18.2 milestone Apr 29, 2020
@peppelinux peppelinux merged commit abfe310 into IdentityPython:master Apr 29, 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.

3 participants