OpenSamlAssertingPartyMetadataRepository should initialize OpenSAML #16042
Comments
|
Hi @jzheaux, Could I work on this issue? |
|
Sure, @ig-jinwoo! It should involve adding the following: static {
OpenSamlInitializationService.initialize();
}to both |
|
Also, note that this ticket is time-sensitive as it is targeting a release on November 18. If you get tied up and aren't able to put together a PR in the next few days, go ahead and let me know and I'll take care of things. |
|
Hi @jzheaux , thank you for providing additional details. I’ll aim to submit a PR as soon as possible, and if I cannot submit the PR by November 13, I’ll let you know. |
ig-jinwoo
pushed a commit
to ig-jinwoo/spring-security
that referenced
this issue
Nov 10, 2024
Closes spring-projectsgh-16042 This commit adds a static initializer block to both OpenSaml4AssertingPartyMetadataRepository and OpenSaml5AssertingPartyMetadataRepository. This ensures OpenSAML is initialized upon class loading, preventing failures when methods like withMetadataLocation are invoked without prior initialization.
ig-jinwoo
pushed a commit
to ig-jinwoo/spring-security
that referenced
this issue
Nov 10, 2024
Closes spring-projectsgh-16042 This commit adds a static initializer block to both OpenSaml4AssertingPartyMetadataRepository and OpenSaml5AssertingPartyMetadataRepository. This ensures OpenSAML is initialized upon class loading, preventing failures when methods like withMetadataLocation are invoked without prior initialization.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
All
OpenSamlXXXcomponents should attempt to initialize OpenSAML.For example, when
OpenSaml5AssertingPartyMetadataRepository#withMetadataLocationis called, the method will fail if another component hasn't already initialized OpenSAML.The text was updated successfully, but these errors were encountered: