Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
gargantext
gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • humanities
  • gargantextgargantext
  • Issues
  • #1

Closed
Open
Opened Sep 05, 2017 by Maziyar@mpanahi
  • Report abuse
  • New issue
Report abuse New issue

Force SSL/TLS to protect user's credentials

Hi Alex,

I think you should force SSL(443) for all online versions of Gargantext. As long as login is required, we should make sure all communications are secured between our servers and clients.

I saw you are using Nginx. I recommend full HTTPS config like:

server {
    listen      80;
    server_name gargantext.org;
    return 301 https://gargantext.org$request_uri;
}
server {
        listen 443;
        server_name gargantext.org;
....

This would force HTTPS for the entire server :)

Screenshot_2017-09-05_13.30.16

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
enhancement
Assign labels
  • View project labels
Reference: humanities/gargantext#1