Hi Eric,

If an account gets locked via a Google data API, you can unlock it
using the API.  Here's some sample code in Java:

    try {
      service = new CalendarService("myOrg-CalendarTest-0.9");
      service.setUserCredentials(USERNAME, PASSWORD);
    } catch (CaptchaRequiredException cre) {
      String captchaToken = cre.getCaptchaToken();
      System.out.println(cre.getCaptchaUrl());
      InputStreamReader isr = new InputStreamReader(System.in);
      BufferedReader stdin = new BufferedReader(isr);
      System.out.print("Enter captcha answer: ");
      String captchaAnswer = stdin.readLine();
      service.setUserCredentials(USERNAME, PASSWORD, captchaToken,
          captchaAnswer);

You can also use this page to manually unlock an account:
https://www.google.com/accounts/UnlockCaptcha

Hope that gets you coding again.

Cheers,
Lane

On Sep 4, 12:58 pm, Eric York <[EMAIL PROTECTED]> wrote:
> I am using ClientLogin with service=cl for authenticating to google
> calendar. Currently my service has a few users. Right now it seems
> that all auth requests are failing. The result is a 403 Forbidden
> message with a CaptchaRequired required error. With some test
> accounts, I went to thecaptchaurl that is supplied in the response
> from google, and responded to that webpage correctly. But ClientLogin
> still fails with the same 403 Forbidden, CaptchaRequired error message
> for those accounts. I know that for the test accounts that I have the
> right password, and answered thecaptchacorrectly. This code had been
> working for sometime. What can I do to fix this problem?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to