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

Fix uncaught error "SessionIndex not an attribute of AuthnStatement" #200

Merged
merged 2 commits into from Dec 4, 2020

Conversation

sebreh
Copy link
Contributor

@sebreh sebreh commented Apr 22, 2020

There is an existing error being thrown from within get_session_info that is not checked by the caller and therefore not forwarded to the callback chain and as such, is causing the module to crash if triggered. Additionally, there was no test case for this error case. This PR includes both the fix to propagate the error and the missing test case.

sebreh and others added 2 commits April 20, 2020 21:41
Propagate thrown error for missing session index
@FreifeldRoyi
Copy link

This is causing major crashes to our service
Please review and approve this PR

@sebreh
Copy link
Contributor Author

sebreh commented Nov 26, 2020

@mcab any chance of getting this into master and the next release?

@mcab mcab self-requested a review December 4, 2020 19:52
@mcab mcab self-assigned this Dec 4, 2020
Copy link
Member

@mcab mcab left a comment

Choose a reason for hiding this comment

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

Makes sense to me. Thanks for adding the test case, as well!

@mcab
Copy link
Member

mcab commented Dec 4, 2020

Ack, I didn't look at inflight PRs too closely.

@sebreh, do you believe that #192 fulfills the issue described here? I believe that the additional try... catch for the entire attribute population here covers the case described by the test case in this PR, as well as describing said test case in this test case.

@sebreh
Copy link
Contributor Author

sebreh commented Jan 18, 2021

@mcab yep, that sounds like it would cover this case. Happy for you to close this after merging that. Thanks!

@mcab
Copy link
Member

mcab commented Jan 25, 2021

@sebreh, I believe that this has been already "closed" due to the merge. I ended up reverting it via #219, so, no-op on your part for this. Thanks for the PR, however!

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.

None yet

3 participants