Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-1281

Apply 'www' to local_mobile check if the call returns 'requirecorrectaccess'

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.5
    • 2.5
    • Log in screen
    • Hide
      1. Configure a Moodle site to use a URL with 'www' (in config.php).
      2. Install local_mobile in that Moodle.
      3. Add that site in the app without entering 'www'. Check that the local_mobile is detected fine. You can also open the "Network" tab in the console and check that 2 calls to local/mobile/check.php are done: one without 'www' and the other with them.
      Show
      Configure a Moodle site to use a URL with 'www' (in config.php). Install local_mobile in that Moodle. Add that site in the app without entering 'www'. Check that the local_mobile is detected fine. You can also open the "Network" tab in the console and check that 2 calls to local/mobile/check.php are done: one without 'www' and the other with them.
    • MOODLE_25_STABLE
    • MOODLE_25_STABLE

      The authentication process is the following:

      1. Check if site exists. We see if we need to use http or https in here.
      2. Check if the app should use local_mobile.
      3. (User inputs credentials).
      4. Try to get user token. If this call returns 'requirecorrectaccess', we add 'www' to the URL and try again.

      The problem is that the local_mobile check also returns 'requirecorrectaccess' if we should use 'www', so the user won't use local_mobile unless he manually inputs those 'www'.

            dpalou Dani Palou
            dpalou Dani Palou
            Frédéric Massart Frédéric Massart
            Juan Leyva Juan Leyva
            Juan Leyva Juan Leyva
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.