Anyone else having a problem with getting Google Docs to play nice with Moodle 2.0? Keeps throwing up an error message for me when I go to Sign In to Google Docs from within Moodle.
Am I missing something? Is it buggy?
A
Can you please be more specific about the error message?
I experience problems, too:
After I select the Google Docs Repository, I click through a couple of screens granting permission for my Moodle to access Google Docs, then at the final screen I get this error:
error/could not upgrade google authtoken to session token
I wonder if it is a bug in the Moodle code??? Any ideas your end?
Same thing happens to me!!!1 Trying to figure it out my self.
Same problem here. Using new Moodle 2.0.1 install, and a Google Apps education site.
We use an http proxy (if that is relevant) proxy is set in Server>HTTP settings
I think I need to upgrade moodle and try again... I haven't installed the latest version of 2.0... That may be the answer
Hi Darren,
Are you using a gapps plugin for Moodle 2.0? I cannot find one for love nor money. This is holding up our move to 2.0. Any help would be appreciated.
We've only used it unsuccessfully in testing. We're stuck on 1.9 for now.
There is a post and potential fix for moodle 2.0 and gapps here:
http://code.google.com/p/moodle-google/issues/detail?id=3
incidentally, our google repository seems to be working now...
When I select the G Docs Repository I am asked to log in. and When I log in, I've got this message:
(what is that "next" parameter about?)
The page you have requested cannot be displayed. Another site was requesting access to your Google Account, but sent a malformed request. Please contact the site that you were trying to use when you received this message to inform them of the error. A detailed error message follows:
The "next" parameter was bad or missing.
I've the same problem. Does anybody have a solution?
I had this same error and it took me months to figure out. First I thought it was a Moodle bug, then a Google API bug. I finally found out what needs to be done.
Google WebApp Management. If you use Google Apps for Education/Business you need to do this. It's a place where you verify the URL where the request originates, in this case, your Moodle server. You can also set up OAuth here as well as certificates. I did not do either of these to get Moodle running.
https://www.google.com/accounts/ManageDomains
Simply verify domain ownership (even if you already verified the same domain for your Apps instance), give it a URL for Moodle and it should work. I did this for each of our Moodle servers and it seemed to work fine after that.
Documentation on this is weak on both Google and Moodle's side. I think it's a recent change on Google's side, actually. I will see if I can get this put in Moodle documentation somewhere.
Thank you so much Drew. You really helped me out.
I hade to perfome OAuth and the certificate to avoid a warning message (insecure website).
Thanks a lot Drew!
I followed your procedure, and everithing now works smoothly :
- go to https://www.google.com/accounts/ManageDomains
- add you Moodle installation domain
- Click your Moodle now listed under "Manage registration"
- Provide the "Target URL path prefix", which in my case was "http://my.moodle.com/repository"
- Click "Save"
Hi,
after domain registration procedure, it show up a web page with this information:
The site moodle.maronio.net is requesting access to your Google Account for the product(s) listed below.
If you grant access, you can revoke access at any time under 'My Account'. moodle.maronio.net will not have access to your password or any other personal information from your Google Account. Learn more
This website is registered with Google to make authorization requests, but has not been configured to send requests securely. We recommend that you continue the process only if you trust the following destination:
http://moodle.maronio.net/ But, when i try to access to Google Docs throught Moodle, i've fot this message:
 |
Google Calendar |
This website is registered with Google to make authorization requests, but has not been configured to send requests securely. We recommend that you continue the process only if you trust the following destination:http://moodle.maronio.net/ But, when i try to access to Google Docs throught Moodle, i've fot this message:
The page you have requested cannot be displayed. Another site was requesting access to your Google Account, but sent a malformed request. Please contact the site that you were trying to use when you received this message to inform them of the error.
Any ideias?
Hi,
after this time, i don't have yet a solution!! Can anyone help me?
Thanks.
Thanks to both, Drew and Nicolas. Your solutions works fine in a 2.1 moodle instalation http://latroupe09.amitikia.com.
Best regards,
Wifred
I was struggling with this all morning - here is the target url prefix that finally worked for me:
https://DOMAIN:443/MOODLEPATH/repository/repository_callback.php
Note the port number - without this it wasn't working (even though the url has https)!
We have a Google Apps for Edu domain (two actually, one for staff, one for students). We don't have SSO enabled. When I add the domain to the list and click Manage XYZ link, it doesn't work for our domain. I get this error:
This service is not available
Google Webmaster Tools is not available for windrush.org. Learn more about Google products you can use with
It seems to be talking about the Webmaster Tools service, which I can't even find as an available option to add to our domain. Any ideas?
Thanks in advance
error/could not upgrade google authtoken to session token
I get exactly that error in an upgraded environment (1.9 - 2.1+) but in a new install on a different server it works "out of the box". In my case this has nothing to do with gapps and the fix presented here in the thread didn't help me with the problem-case... Any other options to fix this and ideas why it works in one place but not in the other?
Hi,
I have a vague recollection that my proxy settings weren't setup correctly in Moodle when I had this error message.
Double-check your proxy address (and username/password credentials if applicable) and retry.
Hope this helps!
Michael
Does anyone have a way to get this working securely?? In order for me to be able to deploy this on our Moodle 2.2.2+ server I need to get rid of the "but has not been configured to send requests securely" message that Google displays. I will not be able to use this repository if our users get presented with that message. We don't want users to get complacent about simply clicking through security warnings. I can get real close via editting lib/googleapi.php and changing secure=0 to secure=1, that makes the security warning go away, but breaks the ability to actually authenticate to the service. We get the following error:
error/could not upgrade google authtoken to session token
We only need this working for the GoogleDocs Repository, all our users authenticate against our local LDAP server, not Google.
Also very interested in this.