I am a technical author and want to trial machine translation with MadCap Lingo. I went to Bing Translate and followed instructions for setting up an azure account. I then filled in the form to deploy Translate Text API to my azure account. The first attempt failed.l I don't think it liked my service name. The second attempt sat running for over an hour and I had an error message displaying saying Gate Way failure. The Cognitive Services service did not respond. So I cancelled that deployment. I tried to fill in the form again but Azure thinks I already have a free deployment and wont let me complete the deployment request. I went back to the dashboard and there are no deployments displaying. So how do I get my trial of Translate text working so I can get a key and link MadCap Lingo to the service?
Related
New Matillion user, and my first project is to read in Google Analytics data by using a google account authorized to access GA data from several clients.
I follow the steps from this Matillion documentation: Google Query Authentication Guide
I have setup the needed client ID and client secret, and I've pasted the redirect URL into the credentials page in the Google console.
From Matillion, I enter the client ID and secret in the OAuth Configuration dialog, and I configure the proxyserver and proxyport under "advanced connection options" as specified in the Matillion documentation.
When I click the Authorization link in the OAuth it opens a new tab to the Google page where I login and allow the access. Once I do this, the redirect seems(?) to kick in and I presented with a browser page with the message "Authorisation complete Please close this tab". I am not taken back to the tab where Matillion OAuth configuration is still waiting for a response of some type.
Any ideas with this? Additional information: I setup Matillion via the Snowflake Partner Connect console and am still in the free 14-day trial for Matillion.
I was able to get the OAuth workflow to finish. Any issues from this point forward will be a battle for another day. Here are my findings:
First note that I initiated my Matillion install from the Snowflake Partner Connect, which was very straight forward. I was up and running with Matillion in less than a minute.
The Matillion version that launched was 1.50.6, which is behind the most current version 1.58.4. I had no idea this would not be the most current version, as I assume the cloud platform might provide new installs with the latest version. I can see reasons why this might not be the case.
After several hours ensuring my GCP project, client id, client key, and other settings were correct everywhere, the workflow still would not complete. I opened a support case with Matillion and it was responded to within 2 hours. That is excellent. The first recommendation was to update Matillion to the latest version as it will address an OAuth issue resembling the one I reported. I saw the new version was very recent, and didn't realize I was nowhere near having the latest version.
After the update completed, I tried repeating all of the same steps. The only difference now was that the "Authorisation complete" tab closed on its own returning me to the Matillion tab which still sat "Waiting for response from service...". The version update seemed to show promise but not a solution.
A comment Schepo above cleared the final hurdle: I removed the proxyserver and proxyport "Advanced Connection options" from the OAuth configuration, and then tried getting a new authorization link. Matillion froze up and the session was dead. I had to close the browser, open a new incognito window and repeat the steps - without the proxyserver/proxyport connection settings. This time the workflow completed!
The Matillion documentation for Google Query: https://documentation.matillion.com/docs/2339840 should be updated if the Proxy Settings are not required for all OAuth configurations. The OAuth issue I reported should also be documented somewhere as a known issue addressable by the latest version (if not already).
OAuth being one of the many ways you can set up connectivity with Snowflake; it appears you're attempting to set up External OAuth, that is Google is the authorizing server. My understanding is that there are two paths to setting up OAuth,
This link has the Azure AD setup with the two options, https://community.snowflake.com/s/article/Create-External-OAuth-Token-Using-Azure-AD-For-The-OAuth-Client-Itself
Googling to setup Google AD returns https://support.google.com/cloud/answer/6158849?hl=en
You may have to follow a similar process, follow this content here: https://docs.snowflake.com/en/user-guide/oauth-ext-custom.html
I've been looking all the answers to this same question, but the solutions seem to be too old or not working...
I am using geocode from the ggmap library in R, I am using it to transform 100,000 addresses to a latitude and longitude...
Everything was working fine for 25,000 and suddenly I started getting the message
"This API project is not authorized to use this API" and now I'm unable to do anything anymore.
I enabled the geocoding API and the google cloud APIs in the google cloud platform..
I also changed the API key, it first said my key expired but after a while it started saying "This API project is not authorized to use this API" again..
As an additional note, my billing method is enabled and working fine
Why do you think this is happening? How to solve it?
well, after an hour or so it seems that it started working again... I assume considering that enabling the geocoding API was the only actual action I did and changing the API key, the only conclusion is that after you do that it's important to wait until all the changes are propagated or something.
We running a wordpress website use google oauth for third-party social login. (via WP Social Login plugin.) Former engineer is leave, and we cannot have past google account credential.
We face a problem shows:
Error 401
Error: deleted_client
The OAuth client was deleted.
but we can only see old client id and secret from website admin panel.
I wanna to know,
if we set up a new google oauth application id/secret, will it make user crash from login website?
Or, is it possible for us to restore/retrieve former application ownership and make it live again?
This happened to me when I was working on an Add-On (maybe not completely related to this question but similar). I mistakenly deleted a Client ID that I thought we weren't using.
How I solved it:
Created a new project in Google Cloud
Associated the Apps Script project (Add-on) to this new Google Cloud project
Then I re-associated the App Script project with my previous Google Cloud project
The previous step will re-compile, create and associate the Client ID to the App Script project. It will contain all settings from the Client ID manually created and associated with your project in the code.
Maybe this will give some light to anyone having a similar problem.
Here use this link:
https://support.google.com/cloud/answer/6251787?hl=en
You have to reach google and they will help you out, this is the only solution you can do.
In my case, the simplest/only path (though certainly not ideal) ended up being to create a new Firebase project and start using that.
This of course can be problematic if you have a lot of data to move and/or a nontrivial data schema - say, with nested collections. For me, it was worth the effort to get unblocked from Sign-In suddenly failing to work.
... ah, OAuth fun
=======
If you are trying to make the new Client ID work .. though it's not a total solution, but after searching for a while, found this config option in Firebase console - where you enable Google Sign In.
So if you generate a new OAuth Client ID, update the ID & secret there.
After I did this, it went from a 401 error to a 400 mis_direct , which I think was step in the right direction.
I'm working on updates of exisitng iOS app which uses LinkedIn REST API.
Earlier to get posts of user I made request to https://api.linkedin.com/v1/people/{id}/network/updates?format=json
I need to get r_network permission to accomplish that. But now with changes in API that request doesn't work. I couldn't find any useful info in Developer Program Transition Guide nor in developer docs.
According to the transition guide, there are only 3 endpoints that are generally available:
Profile API — /v1/people/~
Share API — /v1/people/~/shares
Companies API — /v1/companies/{id}
Your request is clearly not one of these endpoints. If you have not begun a discussion with people in the partnership program, you should start that process now.
I have successfully written a tool to display upcoming calendar events on a website using Google's calendar API (v2). I am using the username/password method outlined at https://developers.google.com/google-apps/calendar/v2/developers_guide_dotnet#AuthClientLogin. Today an instance of this code would not return data or a decent error message. I finally logged into the web server and browsed directly to http://calendar.google.com and logged in using the credentials. I was challenged by Google's captcha and then my code worked.
How do I get around API calls being blocked by Google's captcha security? I don't want to have to re-code for magic cookies but I will if I have to. I have read some about generating tokens but I dont know if that is something I have to do once or every time the code is called.
If your app is a service that is getting used by many people, you might be running into API call bandwidth limitation. That is, google is limiting the number of API requests per time interval.
If this IS getting used by many people, you may have to upgrade to a paid account.