ConnectionDetails for external providers in Spring Security modules

Part of my dev workflow involves using Testcontainers with Keycloak for integration testing against a local, preconfigured IdP/authorization server. It would be awesome if I could use the very same configuration with a running instance through spring-boot-testcontainers, but from what I can tell this isn't currently possible unless the respective configurators implement or expose a ConnectionDetails in some way. (I assume I could achieve something like it if I replace the Spring Security autoconfigurations with my own, but I'd prefer to stick with conventions as much as possible.)

The use cases that come to mind are:

• OAuth2 client provider(s) - URLs defined under spring.security.oauth2.client.provider
• SAML asserting party - Metadata URI defined under spring.security.saml2.relyingparty.registration.<id>.assertingparty
• Probably a few other properties/modules I'm missing

Does this seem like a sensible use case for the ConnectionDetail abstraction? I've noticed the current implementations seem concerned with strictly persistent connections, so perhaps this does not fit the intent. But, since the provider auto-configurations can lead to startup failure when the server is unreachable, the connections at least have some sort of persistent essence.

Review the ConnectionDetails abstraction alongside the OAuth2 client provider and SAML asserting-party configuration paths named in the issue. The payload does not identify files, tests, or a concrete implementation boundary; completion would require an agreed scope and behavior for exposing these external provider details through the relevant auto-configurations.