Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use SSL #40

Closed
boginw opened this issue Apr 15, 2019 · 3 comments
Closed

Use SSL #40

boginw opened this issue Apr 15, 2019 · 3 comments

Comments

@boginw
Copy link
Contributor

boginw commented Apr 15, 2019

Is your feature request related to a problem? Please describe.
As of now, our servers will only respond with HTTP requests. It is highly recommended to switch to HTTPS and redirect all traffic from HTTP over to https as HTTP is considered insecure.

Describe the solution you'd like
We should move to HTTPS

Describe alternatives you've considered
None

@Tekrus Tekrus modified the milestone: Sprint 4 Apr 23, 2019
@holyfailer holyfailer added the info needed Further information is requested label Feb 26, 2020
@holyfailer holyfailer added this to the 2020S1 milestone Feb 26, 2020
@holyfailer holyfailer added this to To do in 2020f 0. sprint via automation Feb 26, 2020
@holyfailer holyfailer moved this from To do to In progress in 2020f 0. sprint Feb 26, 2020
@Lortemanden Lortemanden added this to To do in 2020f 1. sprint via automation Mar 9, 2020
@Lortemanden Lortemanden modified the milestones: 2020S0, 2020S1 Mar 9, 2020
@Lortemanden
Copy link
Contributor

The issues should be moved to the repository where the changes have to be made. We have no idea where it is though.

The http requests from the server should be changed to https request before this issue is solved.

@Lortemanden
Copy link
Contributor

Group 16 had this in 2020 1. sprint

@joandrsn
Copy link
Contributor

For the person assigned this issue:
If you do not know anything about TLS/SSL, please read that first.
Look into Let's Encrypt. Generally these: https://letsencrypt.org/docs/challenge-types/
As far as I can see in the /share-nfs/nginx/ there is already a .well-known-folder. It might seem as if someone already has tried to set it up.

If you're setting Lets Encrypt up, please remember that the certificates expires on 90 days and you should setup a cronjob to create a new certificate.

For changing it on flutter URL, it could be as simple as adding a s here:
https://github.com/aau-giraf/weekplanner/blob/604f6f8973821f65a07a51efd5dec309788f3585/assets/environments.prod.json#L2

@christianhurley christianhurley moved this from To do to Issues in progress in 2020f 1. sprint Mar 13, 2020
@mathiasandresen mathiasandresen self-assigned this Mar 13, 2020
@frederikspang frederikspang self-assigned this Mar 18, 2020
2020f 1. sprint automation moved this from Issues in progress to Issues done Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
2020f 0. sprint
  
In progress
2020f 1. sprint
  
Issues done
Development

No branches or pull requests