spring-cloud / spring-cloud/spring-cloud-consul
Future consul version will no longer support deprecated token authentication through query parameter.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 822
- Forks
- 539
- Avg merge
- 9h 31m
- Merged PRs (30d)
- 7
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Consul API authentication documentation linked in the issue and identify the Spring Cloud Consul entry point for Consul requests. Determine how authentication is currently supplied, then verify that requests can use the X-Consul-Token or Bearer authorization header without the deprecated query parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100