locationtech / locationtech/geomesa
Fix HTTPS certificate for webpage
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Fix HTTPS certificate for webpage
https://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.html
Currently our cert is for github.io, so when you browse from geomesa.org you get invalid cert warnings/blocks.
Likely this can be solved with subject alt names for geomesa.org
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2180
Key: GEOMESA-2180
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Assignee: Jake Kenneally
Reporter: Emilio Lahr-Vivaz
Created: Mon, 12 Feb 2018 09:33:24 -0500
Updated: Mon, 6 Aug 2018 13:55:15 -0400
Comments:
557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Mon, 6 Aug 2018 13:55:15 -0400):
This is partially fixed, but leaving off the www from the url (i.e. geomesa.org) still gives a cert warning.
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 by checking the hosting and certificate configuration for geomesa.org, using the linked Google security guidance as context. Verify that the certificate covers the bare geomesa.org hostname as well as www.geomesa.org, and confirm that browsing the bare domain no longer produces a warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100