I've been trying to test Google Glass Mirror API but I guess it's dead since they've quit its development.
Requests are made to this url (https://www.googleapis.com/mirror/v1,), but it states "Not found". Playground itself is open, but doesn't send anything to the device.
Does anyone know if there's a way of overcoming this? Or if they changed the server location?
Sincerely,
Apidcloud
If you are trying to access the exact URL you specified (https://www.googleapis.com/mirror/v1), it won't work. That isn't a valid endpoint itself for the API. All of the API calls are to URLs that start with that prefix. For example, once authorized, the URL https://www.googleapis.com/mirror/v1/timeline should get the timeline items for the authenticated user. Other paths either retrieve or take action.
If the playground is not sending anything to the device, that is usually an indication that you didn't auth the playground and the device against the same Google account. Make sure you follow the auth directions listed on the Playground page.
Related
I am trying to register OAuth client, following the docs, but none of the links containing /developers in the path are working for me. I am either getting redirected to the https://my.tapkey.com/AdminUI/ and infinite load, until i refresh the page, or getting status code 502 Bad Gateway.
The ones I am having problems with are:
https://my.tapkey.com/AdminUI/developers/oauth-clients
https://my.tapkey.com/AdminUI/developers/identity-providers.
I tried on different OS's, using proxy, but nothing worked for me.
I am trying to register OAuth client, and explore more of the TapKey web api, but this one is a blocker for me.
You caught us here - we have changed the website a bit, and updated documentation is on its way but not yet published. We are working on it right now.
Developer section has moved to Tapkey Integrator Portal available on https://portal.tapkey.io .
Use the same login credentials you are using with Tapkey.
Question:
How do I add the Google Cloud public facing localhost to the authorized domains list so I can set up OAuth?
Background
I'm trying to follow this Google Dev tutorial on Building a Node.js Web App using Google Cloud Platform.
Some of the instructions seem slightly out of date, but I've managed to work around it so far. On Page 9, In section 'Setting OAuth 2.0 Client' step 9 (listed below) it says to paste in the URL https://8080-dot-<9 digit number>-dot-devshell.appspot.com/ with my 9 digit number replaced:
Problem
When I paste in the URI, I'm told that the URI needs to be added to the authorized domains list:
While that's not in the instructions, I went ahead and did as instructed. But every time it goes to 'verify' the domain, it keeps getting a rejection screen saying:
So what on earth do I do here? It won't let me make the OAuth key without the verified domain, and it won't let me verify the domain.
I am guessing the "[...]-dot-devshell.appspot.com" url in 2017 used to forward directly to the web server you wanted to test.
This must have changed in the meantime to require authentication before accessing the web page. This is blocking the configuration of the OAuth since the URL redirects to a different website. This is why you are not able to finish the codelab.
What you could do is try a more recent codelab such as this one to practice with Node.js
I'm trying to connect my website's API and mobile app. I need to authenticate the user with google account but I don't know how to do it.
I created the backend with Django. And I set the endpoint as rest-auth/google/. On the restframework's page, it requires Access Token and Code but honestly I don't get how I can test if it actually works using actual google account.
I want to test from mobile app but I don't understand how and what I need to POST.
Anyone could give me tips?
I would recommend you to use a ready solution like "django-allauth".
If you want to do authentication yourself you might want to read Google's documentation about the topic:
https://developers.google.com/api-client-library/python/
In nutshell you create API credentials:
https://console.cloud.google.com/apis/credentials
Send a user to a link with specific parameters (api-credentials, scope, redirect link etc). Google client can help you to generate it.
A user will login in his account as he would normally do and will give your app permissions to use his information (or won't). After that he will be redirected to the link you specified with GET request with a code as a parameter (or error).
With help of Google client you can exchange the code on a token and then use that token to get information from his profile.
I have an application that uses Google Cloud Translation API for translating contents from a source language to the languages used by the different users.
Since there are several clients for the API, I would like to distinguish the request numbers for different clients, like making a distinction between Android and iOS clients.
There's a dashboard in Google Cloud Translation API Overview page that contains the Traffic chart with a By credential option, which should be able to distinguish the request numbers by their credentials (in our case, API keys.) Unfortunately, it doesn't, the only option available there being Unspecified.
Moreover, even if I change the filter of credentials to No selection, the Traffic map is still the same!
I have also attached the project's credential list, where only API keys are used.
Please help me how to know the request numbers by different API keys, thanks.
Update:
Here are how I send requests to Google Cloud Translation API.
I tried with Postman and Swift code in iOS (what I actually do in my project.) Sent GET/POST requests to the API with API keys and POST requests with service account token, but neither API keys nor service account shown in request logs as the first picture.
Postman
Request with API key in GET
Request with API key in POST
Request with service account token in POST
Swift code
Code
Response
I have also done some requests to Translation API using different credentials. After doing the requests, I have checked my dashboard and I encountered the same situation as you, with all requests marked as Unspecified when choosing the By credential option.
As it turns out, there is an issue related to this situation, as this is not the expected behavior. This has been notified and it will be sorted out by the Google team. You can keep track on any updates related to this issue here. If you click the star button on this site, you will get email notifications whenever any progress has been made. Please bear in mind that it may take some time for this issue to be resolved.
In the meantime, you may consider tracking the client information through the statistics of the applications that make requests to the API, if possible. Thanks for your help on finding this issue.
I've searched on the internet for days now but I can't seem to find any decent example. My understanding of the oauth2 flow is (please correct me if I'm wrong):
client program asks facebook for a request_token
client program starts a browser, giving it an address containing the client_id and the request_token, and yields to the browser
user logs in/subscribes and accepts the request_token
as soon as focus is returned to the client program, the program sends the request_token it got previously to check it's been authorized; if so, an access token is returned
as long as the access_token is valid, the client program is free to access whatever it needed to
This seems to be confirmed by the oauth2 stub and this page, but I can't find any way to get a request_token in facebook. Even here I couldn't find anything useful. Also getting an access_token or a signed_request containing an access_token would be fine.
The platforms my program should run on include MacOSX, iOS, Win32, Linux. We can currently do http/https communication, and platform-specific code such as ShellExecute() on Win32 is acceptable.
Why don't you check out the official docs instead of looking at the documentation of a provider that implements OAuth 1.0?
As Facebook doesn't implement a flow that directly suits your requirements, the next best flow for you to use would be the Client Side Authentication flow.
It basically works like this:
Open some web browser/view from your application and direct it to Facebook's /dialog/oauth endpoint with the parameters as query string.
Let the user log in and grant your application access rights inside it.
Catch the access_token fragment from the response redirection in the browser view.
How you open a web browser/view from your application and how you catch the redirect highly depens on the operating system/libraries you're using, but should be doable with a little research.