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.

Sign up for GitHub

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

Jump to bottom

RequestMatcherMetadataResponseResolver only shows last RelyingPartyRegistration #13700

Closed
jzheaux opened this issue Aug 18, 2023 · 0 comments
Closed

RequestMatcherMetadataResponseResolver only shows last RelyingPartyRegistration #13700

jzheaux opened this issue Aug 18, 2023 · 0 comments
Assignees
@jzheaux
Labels
in: saml2 An issue in SAML2 modules type: bug A general bug
Milestone
6.1.3

Comments

@jzheaux
Copy link
Contributor

jzheaux commented Aug 18, 2023

RequestMatcherMetadataResponseResolver incorrectly computes the key for identifying identical registrations when the entity id contains a placeholder. For example, if each registration has an entity id of http://myapp/{registrationId}, while this means that they are indeed different entities, they will be resolved as the same one, showing only the last registration.
@jzheaux jzheaux added status: waiting-for-triage An issue we've not yet triaged type: bug A general bug in: saml2 An issue in SAML2 modules and removed status: waiting-for-triage An issue we've not yet triaged labels Aug 18, 2023
@jzheaux jzheaux self-assigned this Aug 18, 2023
@jzheaux jzheaux added this to the 6.1.3 milestone Aug 18, 2023
@jzheaux jzheaux mentioned this issue Aug 18, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jzheaux jzheaux

Labels
in: saml2 An issue in SAML2 modules type: bug A general bug
Projects
None yet
Milestone
6.1.3
Development

No branches or pull requests
1 participant
@jzheaux