Issues with mirror.accounts.insert

[GoogleCodeExporter]

I am trying to construct an application with functionality similar to your
example provided on:

https://developers.google.com/glass/develop/gdk/authentication

I am trying to use the mirror.accounts.insert function as described in your 
reference:

https://developers.google.com/glass/v1/reference/accounts/insert

It appears the scope required is not activated on your backend:

https://www.googleapis.com/auth/glass.thirdpartyauth

I have been able to use other parts of the mirror api with success, so it's not 
likely an issue on my side. In fact when i visit the URL above I get a 404 
error in contrast to say other scope urls:

https://www.googleapis.com/auth/glass.timeline
https://www.googleapis.com/auth/glass.location

Original issue reported on code.google.com by aidamina on 30 Apr 2014 at 3:50

[GoogleCodeExporter]

Hello,

This is indeed "WorkingAsIntended", the glass.thirdpartyauth scope is meant to 
be used with a Service Account that identifies your application, not the 
current user.

Unfortunately, you won't be able to test GDK authentication until you give us 
enough metadata to be populated in our back-end (project ID, package name, 
account type, etc.): please do start the review process and specify that you 
are currently testing authentication.

Best,
Alain

Original comment by ala...@google.com on 30 Apr 2014 at 3:57

• Changed state: WorkingAsIntended
• Added labels: Component-Mirror-API

[GoogleCodeExporter]

I am well aware that you require a service account for the access. But even if 
I try to access the service with a service account as described in your 
examples I get a:

com.google.api.client.googleapis.json.GoogleJsonResponseException: 404 Not Found
{
  "code" : 404,
  "errors" : [ {
    "domain" : "global",
    "message" : "Not Found",
    "reason" : "notFound"
  } ],
  "message" : "Not Found"
}

Possibly still "WorkingAsIntended", but the 404 suggests something is broken.

One of the apps I am currently working on isn't for general public, but a b2b 
PoC, so my goal is not for it to be in the MyGlass store. Is it useful at all 
to start the review process from this perspective?

Original comment by aidamina on 30 Apr 2014 at 4:04

[GoogleCodeExporter]

You are getting those errors because we do need metadata from you: this is why 
the review process is required.

Make sure to specify that your Glassware is not meant to be publicly listed and 
is still under development.

Original comment by ala...@google.com on 30 Apr 2014 at 8:12