How to override the behavior of OktaOAuth2PropertiesMappingEnvironmentPostProcessor in a @SpringBootTest about okta-spring-boot

[arvindkrishnakumar-okta]

@danallen88 Thanks for posting!

The discovery of OIDC metadata from .well-known/openid-configuration is done automatically by Spring OIDC client during the registration process and this behavior is embedded inside the Spring Security framework and Okta does not define it. There is no known documented way in Spring framework to bypass this.

For testing purposes, if you have concerns about public internet calls, you could mock the metadata, serve a static metadata by using a framework such as Wiremock. In fact, this SDK has such tests inside oauth2/src/test/ that you can use for reference.

Let me know if that helps!

[danallen88]

Thank you @arvindkrishnakumar-okta for confirming that there is no known documented way in Spring to bypass this, and thank you for pointing me to the tests that shows how Wiremock is used. Is this an example of such a test? https://github.com/okta/okta-spring-boot/blob/master/oauth2/src/test/groovy/com/okta/spring/boot/oauth/env/OktaOAuth2PropertiesMappingEnvironmentPostProcessorTest.groovy

[arvindkrishnakumar-okta]

Sure, please take a look at tests in oauth2/src/test/groovy/com/okta/spring/boot/oauth/.