[bloggerDev] Re: Problem with Non-Gmail Google Accounts - Trevor Johns - com.googlegroups.bloggerdev

21 messages in com.googlegroups.bloggerdev[bloggerDev] Re: Problem with Non-Gma...

From	Sent On	Attachments
Cory W	01 May 2008 13:11
Cory W	01 May 2008 14:13
Jeff Scudder	02 May 2008 09:42
Cory W	05 May 2008 09:27
Jeff Scudder	08 May 2008 10:34
Cory W	12 May 2008 12:54
Jeff Scudder	13 May 2008 14:06
Cory W	14 May 2008 13:04
Cory W	15 May 2008 13:43
Jeff Scudder	15 May 2008 16:42
IC	07 Jul 2008 22:51
serg...@gmail.com	09 Jul 2008 15:15
Trevor Johns	11 Jul 2008 01:38
Trevor Johns	11 Jul 2008 01:55
IC	13 Jul 2008 00:48
IC	13 Jul 2008 00:50
IC	15 Jul 2008 00:01
IC	15 Jul 2008 02:30
Trevor Johns	15 Jul 2008 15:21
IC	16 Jul 2008 23:29
jottos	07 Sep 2008 21:39

Subject:	[bloggerDev] Re: Problem with Non-Gmail Google Accounts
From:	Trevor Johns (tjo...@google.com)
Date:	07/15/2008 03:21:57 PM
List:	com.googlegroups.bloggerdev

Even if the password is the same, it can cause problems. The problem with using HOSTED_OR_GOOGLE is as follows:

- Say a user has two accounts: a Google Apps account, and a regular Google account. Both use the same email address and password.

- The user uses your application and authenticates using the above email address and password.

- When HOSTED_OR_GOOGLE is set, the hosted account will always be preferred.

- However, there's no Google Apps version of Blogger. As a result, the selected account doesn't have any access rights. Any feeds returned will be empty.

If you use GOOGLE instead of HOSTED_OR_GOOGLE, you avoid this problem. Again, there's no Google Apps version of Blogger, so this shouldn't cause any problems.

(I'm assuming that you meant to say that you set the hard-coded value to GOOGLE, setting it to HOSTED shouldn't work).

Let me know if that makes sense. And if you have the time, we'd definitely be grateful for any patches you're able to contribute. :)

On Tue, Jul 15, 2008 at 2:30 AM, IC <ic...@infocrumbs.net> wrote:

On Jul 13, 5:48 pm, IC <i....@infocrumbs.net> wrote:

On Jul 11, 6:39 pm, "Trevor Johns" <tjo...@google.com> wrote:

On Mon, Jul 7, 2008 at 10:51 PM, IC <i....@infocrumbs.net> wrote:

I have a problem that seems similar to this, with one of our customers using Google Apps accounts. But I cannot find the account_type variable or its equivalent in the GData Java Client library. Can anyone point me toward the right direction ?

It seems that the Java version of the library is missing some glue code in comparison to the Python or Javascript releases, especially for managing services.

Taking a quick look through the Java client library, it seems it's currently hard coded to use HOSTED_OR_GOOGLE.

I've filed a ticket to have this fixed:

http://code.google.com/p/gdata-java-client/issues/detail?id=60

If you star the ticket, you'll be automatically notified when this is fixed.

In the meantime, if you feel comfortable editing the client library code (and can remember to undo these changes when the next version of the client library is released), it looks like you should just have to edit the following two lines to change the account type:

src/com/google/gdata/client/GoogleAuthTokenFactory.java:337 svn/trunk/java/src/com/google/gdata/client/GoogleService.java:412

Obviously this is far from ideal, so if you're not comfortable with making these changes yourself, I definitely recommend waiting until the above ticket is fixed.

Thanks for your input trevor, I guessed that would have to be the way to go, but it's good to have a confirmation.

Editing the code should not be a problem, but I am just wondering about what thing though... should HOST_OR_GOOGLE mean it can either be hosted on an external server or by Google ? I don't quite see how it impacts the fact that the editor/owner/poster account is on a Google Apps for your Domain account, but maybe I miss the point somewhere.

Thanks anyway, I'll edit the code when I have time to check if it works when editing this variable.

Hello Trevor,

even though I am still a little confused about why the flag HOSTED_OR_GOOGLE doesn't work, the good thing is it worked by editing the java-client-library's code to use HOSTED instead of HOSTED_OR_GOOGLE for our use case.

we just made a dirty little edit for the moment by switching the hard- coded value, but I guess as soon as we have the time we'll assign someone to write a better patch reflecting the behavior of the python library and post it on the issue tracker's corresponding bug report entry.