Future consul version will no longer support deprecated token authentication through query parameter.

[yapkm01]

According to the excerpt from HashiCorp site:

Deprecating authentication via token query parameter
Providing a Consul ACL token in API requests using the token query parameter is deprecated and will be removed in a future Consul version. Instead, you should provide the token through the X-Consul-Token header or with the Bearer scheme in the authorization header as described in the API authentication documentation.

Future consul version will only support token authentication through header X-Consul-Token or Bearer scheme.
Is there any plan for Spring Cloud Consul to provide support for this new feature especially using the X-Consul-Token header and when will it be available?
Thanks.

[TwinkleTShah]

Hi All/ @spencergibb ,
Is there any tentative plan for this token authentication via X-Consul-Token header?

[tbadalov]

There is a PR in com.ecwid.consul:consul-api to fix this: Ecwid/consul-api#245

However, the project seems to be abandoned.

Edit: An ugly fix could be setting a custom HttpClient when building a ConsulClient with an interceptor that manually adds x-consul-token when there is such a query param