Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed and reviewed
    • Affects versions: 5.1
    • Fix versions: None
    • Components: Documentation
    • Labels:
      None
    • Severity:
      Usability Issue
    • Steps to reproduce:
      Hide
      Our current documentation is not very helpful when it comes to
      explaining the use of Nginx (or any other reverse proxy) with Opencast to
      provide a proper HTTPS set-up despite this being the de-facto standard
      for most Opencast installations.

      This patch adds that documentation, while improving the general
      structure of the HTTPS documentation and making it more important in the
      general table of contents.

      Note that the Nginx example included here is a minimal set-up, not
      focused on security. A few general security hints will probably follow.
      Show
      Our current documentation is not very helpful when it comes to explaining the use of Nginx (or any other reverse proxy) with Opencast to provide a proper HTTPS set-up despite this being the de-facto standard for most Opencast installations. This patch adds that documentation, while improving the general structure of the HTTPS documentation and making it more important in the general table of contents. Note that the Nginx example included here is a minimal set-up, not focused on security. A few general security hints will probably follow.

      TestRail: Results

        Attachments

          Activity

            People

            • Assignee:
              lkiesow Lars Kiesow
              Reporter:
              lkiesow Lars Kiesow
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                TestRail: Cases