-
Notifications
You must be signed in to change notification settings - Fork 358
[Maintenance] Review use of SamlHTTPMetadataResolver #2932
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or requesttriagedIssues labeled as 'Triaged' have been reviewed and are deemed actionable.Issues labeled as 'Triaged' have been reviewed and are deemed actionable.
Description
Is your feature request related to a problem?
During review of #2927, @cwperks mentioned that the main reason of why we still use HTTP commons 4 is SamlHTTPMetadataResolver which reads IDP metadata file and track the state of it.
The new version 4.3.0 still use HTTP commons 4 though.
What solution would you like?
To exclude HTTP commons 4 completely there are 2 options exists:
- Implement our own solution which will use HTTP common 5. For that we need to extend
org.opensaml.saml.metadata.resolver.impl.AbstractReloadingMetadataResolverand implement almost the same logic asorg.opensaml.saml.metadata.resolver.impl.HTTPMetadataResolverwhichSamlHTTPMetadataResolverextends. - Try to prepare PR in
Shibbolethrepository with new version (do not know what is the process since repo is not GiHub one)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requesttriagedIssues labeled as 'Triaged' have been reviewed and are deemed actionable.Issues labeled as 'Triaged' have been reviewed and are deemed actionable.