-
Bug
-
Resolution: Fixed
-
Minor
-
4.1
The OAuth process launched by the app does not complete (the user is able to log in but it is not redirected back to the app) when new policies requiring agreement are added to the site. This could also happen the first time they access to the site if there is a mandatory license.
I've reproduced this with new users but I think it would happen the same for existing policies when a new mandatory policy is added to the site.
There is a more detailed description here: MOBILE-4078
Reproduction steps
On the Moodle site (LMS) as a site administrator:
- Add a site policy (Site administration > Users > Privacy and policies > Policy settings). It can be either 'Default (core)' or 'Policies (tool_policy)' as it happens on both.
- Configure Google OAuth
- Create a user account with OAuth2 authentication method, use a Google account email. (You need to be able to log in using that account.)
On a mobile device:
- Open a browser and log in on that Google account
- Open the the Moodle app and add the Moodle site (LMS)'s URL
- Tap on the Google authentication
- (If you have more than one Google account you will need to select first which want you want to use)
- Accepts the pending policy(ies) in the browser
- You will see an error message and you will NOT be redirected back to the app
Workaround: Change the Type of login (tool_mobile | typeoflogin). Site administration > Mobile app > Mobile authentication, to via a browser window or via an embedded browser. (For more information please visit the Moodle app guide for admins - Mobile authentication: SSO authentication method.)
- Discovered while testing
-
MOBILE-4078 Facebook login fails sometimes when receive unexpected token
- Closed
- Testing discovered
-
MDL-80721 Authentication: MFA is breaking the OAuth process in the mobile app
- Closed