如何为Feign Client设置与当前请求不同的Authorization Header？

Got it, let's break down how to make your Feign Client send a different Authorization header than the one received by your service. Here are two practical approaches depending on your use case:

1. Custom Feign RequestInterceptor (Global or Client-Specific) #

This is perfect if you want all requests from a particular Feign Client (or all Feign Clients) to use the custom Authorization header automatically.

Step 1: Create the RequestInterceptor #

Implement RequestInterceptor to override or add the new Authorization header. You can pull the token from configuration, fetch it dynamically from another service, or use a secure provider—just avoid hardcoding it directly in code:

import feign.RequestInterceptor;
import feign.RequestTemplate;
import org.springframework.beans.factory.annotation.Value;
import org.springframework.stereotype.Component;

// Use @Component for global application to all Feign Clients
// Or use @Configuration if you want to limit it to specific clients
@Component
public class CustomFeignAuthInterceptor implements RequestInterceptor {

    // Pull custom token from application.properties/yaml
    @Value("${external.service.auth.token}")
    private String customAuthToken;

    @Override
    public void apply(RequestTemplate template) {
        // Safely remove any existing Authorization header first
        template.removeHeader("Authorization");
        // Add your custom Authorization header (adjust scheme if not Bearer)
        template.header("Authorization", "Bearer " + customAuthToken);
    }
}

Step 2: Attach to Your Feign Client #

If you used @Component, this interceptor applies to all Feign Clients. To restrict it to a single client, use the configuration attribute in your @FeignClient annotation:

import org.springframework.cloud.openfeign.FeignClient;
import org.springframework.web.bind.annotation.GetMapping;

@FeignClient(name = "external-service", configuration = CustomFeignAuthInterceptor.class)
public interface ExternalServiceFeignClient {

    @GetMapping("/api/data")
    String fetchExternalData();
}

2. Dynamic Header Per Feign Method #

If you need to pass a unique token for each method call (instead of a fixed global one), use @RequestHeader directly in your Feign Client interface:

import org.springframework.cloud.openfeign.FeignClient;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestHeader;

@FeignClient(name = "external-service")
public interface ExternalServiceFeignClient {

    @GetMapping("/api/data")
    String fetchExternalData(@RequestHeader("Authorization") String customAuthHeader);
}

Then, when calling this method from your service, pass the custom header value (generate or retrieve it based on your logic):

@Service
public class MyService {

    private final ExternalServiceFeignClient feignClient;

    // Constructor injection (preferred over @Autowired)
    public MyService(ExternalServiceFeignClient feignClient) {
        this.feignClient = feignClient;
    }

    public String handleIncomingRequest() {
        // Logic to get your custom token (e.g., call a token service, fetch from cache)
        String customAuthHeader = "Bearer " + getFreshCustomToken();
        return feignClient.fetchExternalData(customAuthHeader);
    }

    private String getFreshCustomToken() {
        // Replace with your actual token retrieval logic
        return "your-dynamic-custom-token-456";
    }
}

Key Notes #

• Header Override: If your Spring Cloud setup automatically propagates incoming headers, make sure your interceptor explicitly removes the original Authorization header before adding the new one (as shown in the first approach).
• Security Best Practices: Never hardcode tokens—use environment variables, Spring Cloud Config, or a secure token provider service. For expiring tokens, add caching logic to your interceptor to avoid fetching a new token on every request.
• Scheme Flexibility: Adjust the header value format if your external service uses a different auth scheme (e.g., Basic instead of Bearer).

内容的提问来源于stack exchange，提问作者Govardhana krishnan B