Cannot get a correct setup of SSL certificates
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 57
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
I'm currently putting up an up-to-date Drifter environment on Ubuntu 18.04 with a LAMP stack for an HTTPS API project. I've set `ssl: yes` in `virtualization/parameters.yml`. After the provisioning, it generated a `ca.crt` file in my web root.
I've tried importing it in my "truststore", as stated in the doc, with the command `keytool -v -import -file ca.crt -alias projectname -keystore my-cacerts`. It had no output. I've restarted my Chrome (and then my computer), and Chrome still gives the same warning `NET::ERR_CERT_AUTHORITY_INVALID` when I access the API in HTTPS.
Am I missing something ? Did anyone set up a SSL certificate and could explain me the missing steps ?
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 virtualization/parameters.yml and the SSL setup described in the documentation; reproduce provisioning on Ubuntu 18.04 and inspect how ca.crt is generated and trusted by Chrome. Done means the provisioned HTTPS API opens without NET::ERR_CERT_AUTHORITY_INVALID and the missing steps are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ubuntu
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100