Failed to load remote configuration

[bfs-natewallman]

After updating from 1.2.18 to the latest version I noticed swagger-ui isn't working anymore. When I bring it up I just get a message about "Failed to load remote configuration." I'm using a pretty vanilla configuration. Is there a migration step that isn't documented?

[bfs-natewallman]

The following is what I see. I'm still trying to track down what changed.

[m-kay]

If you are using spring-security you have to include the config path in your sercurity configuration.
What I did in my security config was to exclude those paths from websecurity.

@Configuration
public class WebSecurityConfiguration extends WebSecurityConfigurerAdapter {
	@Override
	public void configure(WebSecurity web) throws Exception {
		web.ignoring().antMatchers("/swagger-ui/**", "/v3/api-docs/**");
	}
}

[bfs-natewallman]

I had that before but I didn't have the wild card on the end as it wasn't needed. Thanks for the tip!

[saiteja-konda]

It worked for me, Thank you

[farrukhnajmi]

In my case the issue was that I had changed by service's context path to include a version but in the swagger UI url I included it in only one place instead of two.

Correct Swagger UI URL:
http://localhost:8081/myservice/v3.0.0/swagger-ui/index.html?configUrl=/myservice/v3.0.0/api-docs/swagger-config

Incorrect Wagger UI URL causing the error:
http://localhost:8081/myservice/v3.0.0/swagger-ui/index.html?configUrl=/myservice/api-docs/swagger-config

Above is missing v3.0.0 in configUrl query parameter

[ZelalemGizachew]

Adding this "/v3/api-docs/**" as one of the WHITELISTED urls fixes the problem.

`
private static final String[] AUTH_WHITELIST = {
"/authenticate",
"/swagger-resources/",
"/swagger-ui/",
"/v3/api-docs/",
"/api/v1/app/user/auth/"
};

@Bean
public SecurityFilterChain securityFilterChain(HttpSecurity httpSecurity) throws Exception {
    httpSecurity
            .csrf(AbstractHttpConfigurer::disable)
            .authorizeHttpRequests(
                    auth -> auth.requestMatchers(AUTH_WHITELIST).permitAll()
                            .anyRequest().authenticated()
            )
            .sessionManagement(session -> session.sessionCreationPolicy(SessionCreationPolicy.STATELESS))
            .authenticationProvider(authenticationProvider)
            .addFilterBefore(jwtAuthFilter, UsernamePasswordAuthenticationFilter.class);
    return httpSecurity.build();
}

`

[lo-rodriguez]

A query. If I do not have the spring security dependency included, then I must include the Snippet which has been mentioned in the previous comments. If not, what should I do?

[ZelalemGizachew]

A query. If I do not have the spring security dependency included, then I must include the Snippet which has been mentioned in the previous comments. If not, what should I do?

If you are not using the Spring Security Dependency, adding the swagger dependency is enough to load your apis in Swagger. I understand your question...

[Mauricio-Carrion]

I have the same issue when I deploy my spring boot app behind a nginx reverse proxy using docker. In localhost, swagger works fine.