Yesterday an issue come in from a user experiencing 401 errors from a 
request using the Google Apps Profiles API. I tested it on my domain, and 
worked fine so assumed they had not enabled OAuth access from the cPanel or 
something like that.

However, today I had 2 more issues about the same thing, so I did some more 
digging. I have a number of Google Apps domains, and discovered that I 
was experiencing the same issue on one of my domains. Rechecking the 
documentation, I noticed that the profiles API scope had changed from *
https://www.google.com/m8/feeds/* to *
https://www.google.com/m8/feeds/profiles*. I updated my manifest and scope 
variables and the code started working again.

It seems that Google have created a new scope for the Profiles API, which 
makes sense, as it was previously the same as the contacts API.

However, what I can't figure out is why it worked on my other domains with 
the wrong scope. Is this a new change that is being rolled out and therefore 
effected only some domains and not others?

Further, I didn't see any announcement of a new scope. Was there one? It 
would have been useful to know about it beforehand so I could have prevented 
my app from breaking in advance! The same thing happened last May (right in 
the middle of IO in fact, so I had to fix stuff during the conference! ), 
when Google changed the scopes for some of the Admin 
APIs<http://code.google.com/googleapps/support/domain_info_and_management_forum.html?place=msg%2Fgoogle-apps-mgmt-apis%2FpxLVtHfPDdE%2FN6a7WMifjvIJ>
.

Anyone else getting the same issues or have any info on this?

-- 
You received this message because you are subscribed to the Google
Groups "Google Contacts, Shared Contacts and User Profiles APIs" 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://code.google.com/apis/contacts/community/forum.html

Reply via email to