Skip to content

A null SingleLogoutServiceLocation should not cause a NullPointerException #10674

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

Closed
jzheaux opened this issue Jan 3, 2022 · 0 comments
Closed
Assignees
Labels
type: bug A general bug
Milestone

Comments

@jzheaux
Copy link
Contributor

jzheaux commented Jan 3, 2022

See #10607.

Since not every tenant in a given application will use SAML 2.0 Logout, it should be possible to use saml2Logout in the DSL while indicating a null single logout service location given RelyingPartyRegistration instances.

@jzheaux jzheaux added type: bug A general bug type: breaks-passivity A change that breaks passivity with the previous release labels Jan 3, 2022
@jzheaux jzheaux added this to the 5.7.0-M1 milestone Jan 3, 2022
@jzheaux jzheaux self-assigned this Jan 3, 2022
@jzheaux jzheaux changed the title RelyingPartyRegistration should not provide a default logout endpoint A null SingleLogoutServiceLocation should not cause a NullPointerException Jan 3, 2022
@jzheaux jzheaux removed the type: breaks-passivity A change that breaks passivity with the previous release label Jan 3, 2022
jzheaux added a commit that referenced this issue Jan 3, 2022
@jzheaux jzheaux closed this as completed in cb008fa Jan 3, 2022
jzheaux added a commit that referenced this issue Jan 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant