Filters are not applied to Actuator endpoints when management port is different

[thibauult]

I noticed that some of my custom filters are not applied to Actuator endpoints when a different management port is defined.

Even using :

@ManagementContextConfiguration
public class MicroServiceManagementAutoConfiguration {

  @Bean
  public FilterRegistrationBean<TestFilter> testFilter() {
    final FilterRegistrationBean<TestFilter> registrationBean  = new FilterRegistrationBean<>();

    registrationBean.setFilter(new TestFilter());
    registrationBean.addUrlPatterns("/*");

    return registrationBean;
  }
}

// registered in META-INF/spring.factories#org.springframework.boot.actuate.autoconfigure.ManagementContextConfiguration

The TestFilter is successfully applied when management.server.port == server.port but never applied when management.server.port != server.port.

[wilkinsona]

#9560 is related to this. We have an inconsistent story around what is and isn't applied and configured when a separate management port has been configured that we'd like to straighten out. This is another part of that.

[dnsymphony]

This is a pretty big deal. That linked ticket is from 2017. It doesn't seem like this is getting the attention it deserves. Having the actuator endpoints on a different port is a critical security requirement for us (I work with Thibault). Not being able to configure our standard filters that add tracing, logging, auditing, etc. on these endpoints is a serious problem.

[wilkinsona]

I would expect it to work with @ManagementContextConfiguration. I'll take a look and see why that's apparently not the case.

[wilkinsona]

A filter defined in a @ManagementContextConfiguration class works for me when a separate management port has been configured. Can you please provide a minimal sample that reproduces the behaviour you're seeing where it's only effective when the server and management ports are the same?

[dnsymphony]

@ManagementContextConfiguration was the first approach I had tried but it didn't work. I went back and looked at it again since you said it was working and realized that my class with that annotation was still being scanned by the main application context scanner even though I thought I had excluded it. Once I fixed the exclusion, it worked. Thanks for verifying it was working with two different ports and forcing me to go back (yet again) and revisit my code. You can close this ticket. Thanks for the help.

[wilkinsona]

Great, thanks for following up. We'll leave the issue open as we'd like to offer an alternative that doesn't require the use of @ManagementContextConfiguration.

[dnsymphony]

OK. Any idea what I need to do to get my custom ErrorController to work for the management port?