Hello fellow Moodlers,
I've set up the Moodle Mobile additional features using the instructions in the docs, and I've installed a fresh copy of Moodle Mobile 1.10 from Google Play.
Relevant versions info:
- Moodle 2.7.3+ (Build: 20141218)
- Galaxy Note 2 w/KitKat (4.4.2)
- Moto X (also w/KitKat 4.4.2)
- Moodle Mobile additional features version 2.7.10 (2014060409)
We're using CAS authentication, so I've set "Type of Login" to "Via a browser window".
I open the app and enter my Moodle installation's base URL ( www.myschoolname.edu/moodle2 ) and I get the "You need to log in to the site in a browser window." message as I'd expect. I tap "Yes", and the stock android browser opens with the correct CAS login page.
I log in to CAS with an instructor account (non-admin), and the browser proceeds to the site. I am logged in as the instructor, but I get an unexpected warning "Automatically token generation is not available to site administrators (they must create a token manually in the site)". From there, I can use the mobile website as normal, but I am not directed back to the app.
If I return to the Moodle Mobile app, I am back where I started. I enter the base URL for my Moodle installation, and it prompts me to open a browser again, but now that I already have a CAS session I am immediately directed to the odd-looking URI:
moodlemobile://token=MWM5MzQ4xxxx
This has a normal looking random token string but of course the browser has no idea how to handle the protocol "moodlemobile".
Because of the unexpected warning about token generation, I paid extra attention to the moodle/webservice:createmobiletoken and :createtoken role overrides, both of which are set to "Allow" for the Authenticated User role.
Has anyone else seen CAS authentication under similar conditions?
Thanks for any input or pointers,
Nate