Android nrF beacon for Eddystone

[Tom Howard]

Hi,

I would be grateful if you advise on the OAuth client id's required when developing the android nrF beacon for Eddystone.

From reading the nrF beacon for Eddsytone source code on GitHub it is clear the app enables server side access as outlined here; developers.google.com/.../offline-access. This requires a web application client ID for the backend server, which is different to the client ID of the app. So;

- Is this backend server Google's authorisation server. 

-  Where is the client ID of the app used, and is it stored in the app like the API key

- Does the client ID of the app enable the user from accessing the Proximity beacon API based on whether they have owner or editor rights in the console project.

Thanks

[Roshan Rajaratnam]

Hi, in this case yes, it's authorized against google's authorisation server. Client ID is something you create on the console, and is used when authorozing a user. Once authorized you get an access token and a refresh token. Use the access token to access the proximity beacon api. When your access token expires use the refresh token to get a new one. You will find more information here developers.google.com/.../OAuth2

[Tom Howard]

Thanks for your response. Would it be possible to confirm that this is an OAuth client ID for Android rather than and OAuth client id for web application? If this is not the case then what is the use case for the OAuth client id for web application that the android nrF beacon suggests to create.  

[Roshan Rajaratnam]

Hi, nice catch yes we did use a web application client id at the time as there was something wrong while trying to use the Android OAuth client id.  But haven't gotten around to check if it does now.