The controller's CA cert is invalid and missing SANs and CN is invalid
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 40/100
Research direction
Start by tracing how the controller charm generates its CA certificate and publishes it through relation data, then inspect the certificate with openssl as shown in the issue. Done means the certificate includes SAN entries for the unit IP and DNS name, uses a valid CN, and lets the collector scrape /introspection/metrics without skip_insecure_verify.
Written by the indexing model from the issue text.
Description
When the controller charm is related to e.g. Opentelemetry Collector, it provides its ca cert through relation data so that the collector can scrape the controller's metrics on port 17010 at /introspection/metrics.
The scrape job tells us to scrape over unit IP, however, the cert does not have a SAN IP. Also, the SAN DNS is also missing and the CN is technically invalid. This means that the collector has to do skip_insecure_verify to scrape.
This is the result of looking at the cert with openssl
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
31:d3:da:eb:54:a3:01:fa:10:6e:fa:3b:df:e6:bc:c1:c0:cb:01:00
Signature Algorithm: sha256WithRSAEncryption
Issuer: O = Juju, CN = juju-ca
Validity
Not Before: Jul 2 13:47:34 2025 GMT
Not After : Jul 2 13:52:34 2035 GMT
Subject: O = Juju, CN = juju-ca
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (3072 bit)
Modulus:
...
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Key Usage: critical
Digital Signature, Key Encipherment, Certificate Sign
X509v3 Basic Constraints: critical
CA:TRUE
X509v3 Subject Key Identifier:
58:94:AC:C5:B8:DB:9F:2A:7F:B1:FC:D8:D9:63:00:65:B1:1F:B8:F2
Related Issues:
- Dominant language
- Python
- Stars
- 3
- Forks
- 21
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from juju/juju-controller
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
juju/juju-controller#155 ·
-
metrics-endpoint-relation-created hook fails with ValueError on k8s when bind_address returns service FQDNMay be free again @gfouillet claimed this 89 days ago, and no pull request is open. Open
juju/juju-controller#130 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
juju/juju-controller#112 · 10 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
juju/juju-controller#93 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
juju/juju-controller#92 · 1 comment ·
All issues in juju/juju-controller
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
snap-stanford/Biomni#380 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/playwright-python#3361 ·
Maintainers usually reply within 1 day
-
documentation priority: low size: S status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cubrid-lab/sqlalchemy-cubrid#1397 ·
Maintainers usually reply within 1 day
-
documentation priority: low size: S status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cubrid-lab/pycubrid#1307 ·
Maintainers usually reply within 1 day
-
[Bug]: Installer hides SSL certificate errors as bare URLError, and the suggested fix can't workOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ShaftHQ/chaosengine-harness#143 ·
Maintainers usually reply within 1 day