eureka: Custom clientFilter is useless

Asked Nov 27 '17 at 09:39

Active Nov 03 '18 at 17:57

Viewed 376 times

For more complex needs you can create a @Bean of type DiscoveryClientOptionalArgs and inject ClientFilter instances into it, all of which will be applied to the calls from the client to the server.

this description in spring-cloud wiki

@Bean
    public DiscoveryClientOptionalArgs discoveryClientOptionalArgs() {
        DiscoveryClientOptionalArgs discoveryClientOptionalArgs = new DiscoveryClientOptionalArgs();
        discoveryClientOptionalArgs.setAdditionalFilters(Collections.singletonList(new IpCilentFilter()));
        return discoveryClientOptionalArgs;
    }


public class IpCilentFilter extends ClientFilter {
    @Override
    public ClientResponse handle(ClientRequest clientRequest) throws ClientHandlerException {
        // here How to disallow clients to connect
        return getNext().handle(clientRequest);
    }
}

How to disallow clients to connect?

throws ClientHandlerException useless
return null useless

what should I do？

edited Nov 03 '18 at 17:57

Cœur

37,241
25
195
267

asked Nov 27 '17 at 09:39

giegie wang

1

Can you expound on what "useless" means? What are the actual results when you try these things? My guess (I've not written a Jersey client filter before) is that you'd return an appropriate `ClientResponse`. – spencergibb Nov 27 '17 at 16:39
for example, can clientFilter prohibit an IP connection to eureka? How to achieve it – giegie wang Nov 28 '17 at 01:43
You know this is a client side filter correct? It won't restrict anything on the eureka server. – spencergibb Nov 28 '17 at 01:49
I understand it wrong, I go to learn jersey clientFilter – giegie wang Nov 28 '17 at 02:14
You can write a custom security filter on the eureka server side and have custom security. – Indraneel Bende Feb 19 '18 at 04:55

eureka: Custom clientFilter is useless

0 Answers0