Does consul supports chained SAN certificates?
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
Does the consul supports chained SAN certificates? We are repeatedly getting the following errors
~~~
consul[xxx]: consul.rpc: failed to read byte: tls: failed to verify client's certificate: x509: certificate specifies an incompatible key usage: leaf contains the following, recognized EKUs: 1.3.6.1.5.5.7.3.1 from=xxxx:xxx
consul[xxxx]: consul: error getting server health from "xxxxxhost-namexxx": rpc error getting client: failed to get conn: remote error: tls: bad certificate
~~~
The log:
~~~
consul[xxx]: consul.rpc: failed to read byte: tls: failed to verify client's certificate: x509: certificate specifies an incompatible key usage: leaf contains the following, recognized EKUs: 1.3.6.1.5.5.7.3.1 from=xxxxx:xxx
~~~
Is not occurring anymore but "tls: bad certificate" still persists.
Contributor guide
Research direction
Start by reviewing Consul's TLS certificate handling against the reported x509 key-usage error; the issue names no source file or test. Determine whether chained SAN certificates are supported and explain the remaining "tls: bad certificate" error, documenting a reproducible conclusion or required change.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100