Iam developing a multi lingual application and planning to use google translator API. I was wondering if Google Translate API supports OAuth authentication or not, document is available for using key but no information is available regarding OAuth authentication.
Thanks
Related
I am reading microsoft documentation and using their apps / api to secure api using Azure AD.
But I got confused by two different approaches and as articles describe setting up the client app and Api.
This article describe " Protect a web API backend in Azure API Management using OAuth 2.0 authorization with Azure Active Directory"
link: https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-protect-backend-with-aad
I am following another tutorial and using built application for web app and api, this describe
"How to secure a Web API built with ASP.NET Core using the Microsoft identity platform. This sample demonstrates a ASP.NET Core Web App calling a ASP.NET Core Web API that is secured using Azure AD".
It further describe "1. The client ASP.NET Core Web App uses the Microsoft Authentication Library (MSAL) to sign-in and obtain a JWT [Access Tokens].
2. The [Access Tokens] is used as a bearer token to authorize the user to call the ASP.NET Core Web API protected by Azure AD.
So I am confused are they two different things if so when to use 2nd option or first 1. Both deals with the Azure AD and claims to protect an api.
The first article you're referring to uses Azure API management, where authentication is taken away from your API and completely configured in API management. This means you're adding an extra Azure resource type to your eco-system, most probably also adding costs.
In this article, you'll learn how to configure your Azure API Management instance to protect an API, by using the OAuth 2.0 protocol with Azure Active Directory (Azure AD).
Next tot this, API Management adds a lot of other functionality as well.
In the second article you learn how to implement authentication using Microsoft Identity Platform. This way you will not be adding Azure resource types, but you'll have to code the authentication yourself.
A client has requested implementation of the new Google Photos API as a feed of their photos on the website.
The issue arises whereas the library only supports OAuth 2.0 to authorise the library requests. Meaning that each visitor needs to authenticate themselves prior to seeing the photos.
Authorization
Like other Google REST APIs, the Library API uses OAuth 2.0 to handle authentication and authorization. Your app can request access to the user's Google Photos library via the various authorization scopes provided by the API.
Note that the Library API does not support service accounts; to use
this API, users must be signed in to a valid Google Account.
Does anyone know a way that I can authenticate the library for all web traffic? I want to use Google Photos as a CMS for images and have a constant feed on the site.
Since the Google Photo APIs requires OAuth 2.0 User Credentials, you will not be able to use this API as a CMS for you website.
Each API request requires an OAuth Token and this token can only be obtained by a person authenticating with Google Accounts. The OAuth Flow requires the user to authenticate and grant permission to their personal Google Account.
In addition this API requires that you create OAuth Client Secrets which is used to track your app.
I have been playing with the new Admin SDK in conjunction with the "upgraded authorisation experience" and wondered if someone has and experience/examples on how to use it. From what I have read, if you upgrade the authorisation experience you shouldn't need to use OAuth 2.0 and get a client ID and secret from the API console.
When you upgrade the authorisation, the API console entry is automatically created so you just have to turn on Admin SDK. Your app should then run simply using your own admin credentials.
Have I misunderstood this and if so, what is the benefit of the new authorisation experience?
I can use the Admin SDK just fine if I create a client ID and secret in the API console but this is using OAuth 2.0 then.
If someone has an example of how to use the admin sdk with OAuth 1.0 i could have a look at it would be much appreciated.
You will still need get your tokens and API key...
Take from the Directory API documentation:
If your application has certain unusual authorization requirements, such as logging in at the same time as requesting data access (hybrid) or domain-wide delegation of authority (2LO), then you cannot currently use OAuth 2.0 tokens. In such cases, you must instead use OAuth 1.0 tokens and an API key. You can find your application's API key in the Google APIs Console, in the Simple API Access section of the API Access pane.
If you are looking for an oAuth2 example with GAS, Arun has a nice example he posted on GitHub, see the SO posting: How to authorize with oauth 2.0 from appscript to Google APIs?
Sorry, I don't have any oAuth1 example to interface with the new APIs.
I am developing web application which consists of a Silverlight application and a REST API. An optional use case is that the customer may also want to integrate with Salesforce. By "integrate" I mean utilize SSO with Salesforce when logging into my application as well as access data via Salesforce's REST API. The current hurdle I can't seem to get over is that SSO uses WS-Federation while Salesforce's REST API uses OAuth 2.0. What is the best way to being these two authentication mechanisms together?
My knee-jerk reaction was for my Federation Provider STS to acquire an OAuth access token from Salesforce and add it as a claim to the security token received from Salesforce's Identity Provider STS, but I think this might require me to write a custom STS. I'd rather not do that. Is there a better way?
This question is old but comes up often, so ...
There is now information on how to do this here
Configuring-SSO-to-SharePoint
This approach uses WS-Fed.
Is there anyway to retrieve the Google Oauth refresh_token using Scribe?
I am building an app that requires several scopes mixed between java Gdata and Google api java client libraries -- and I am looking for a Single Sign On (SSO) when a user of my app signs in. However because of the state of current Google Apps API's requiring Oauth 1 or Oauth 2 depending on which library / scope you need, I'm a bit stuck.
Oauth 1 (java gdata e.g. analytics data export scope) - requires the
access_token secret
Oauth 2 (google api java client e.g. analytics calendar scope) -
require a refresh token, which is not avail currently in a Scribe OAuth 1 call
Any tips / advice? Anyone managing this with a single sign on?
Sorry scribe does not support (at the time of this writing) Google's OAuth 2.0 Apis.
It shouldn't be too hard to implement using FacebookApi as a guide. Cheers!
Scribe has added support for Google OAuth API. I used scribe 1.2.2 and it worked just fine for me.