The SIO2 project
  1. The SIO2 project
  2. SIO-1607

ForceIPDNSAuth middleware is still active after end of contest exclusiveness

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: Current Version
    • Fix Version/s: None
    • Component/s: OIOIOI
    • Labels:
      None

      Description

      When you set up a contest of onsite-type, like OI Onsite, the ForceIPDNSAuth middleware will require that the user is authenticated through his/her IP or DNS. But It will behave this way as long as the middleware is included in settings.py, but the intended behavior is to block access only to ongoing contests. This forces (pun intended :P) the admins to comment and uncomment the middleware in the settings.py file.

      I suppose that coupling this middleware with contest-exclusiveness would work as expected, but this idea has to be verified.

        Issue Links

          Activity

          Connect your code to JIRA

          Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.

          Git & Mercurial in the cloud

          Collaborate across unlimited private code repositories.

          Git behind the firewall

          Manage and collaborate on Git repositories behind a firewall.

          Browse and search code

          Browse, search, and track source code repositories.

            People

            • Assignee:
              Szymon AcedaƄski
              Reporter:
              Maciej Matraszek
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: