I've been using Oauth Plugin for LinkedIn authentication with salesforce for a few months now without any issues; today we are seeing this error with no change to our existing code. I verified that the API keys and the scope were correct on the LinkedIn Developer site. Anyone know how to solve this issue?
ERROR:
Failed getting a request token. HTTP Code = 403. Message: Forbidden.
Response Body:
oauth_problem=Scope%20NOT_AUTHORIZED%20%3A%20r_fullprofile%2C%20Scope%20NOT_AUTHORIZED%20%3A%20r_network%2C%20Scope%20NOT_AUTHORIZED%20%3A%20rw_groups%2C%20Scope%20NOT_AUTHORIZED%20%3A%20rw_nus%2C%20Scope%20NOT_AUTHORIZED%20%3A%20w_messages
Endpoint=https://api.linkedin.com/uas/oauth/requestToken?scope=r_fullprofile%20r_emailaddress%20r_network%20r_contactinfo%20rw_nus%20rw_groups%20w_messages, Method=GET]
They have made some changes to the LinkedIn API. Have a look at Developer Program Transition Guide
Related
I am providing an application that performs OAuth 2.0 authentication using Microsoft IDs, but the other day an error suddenly occurred and the authentication could not be performed, and the situation is still continuing.
It was working fine until then.
We are using the admin_consent API to get tokens, as shown in the following URL.
https://learn.microsoft.com/ja-jp/graph/auth-v2-service
Now, before going to the Microsoft login screen, we are redirected to a URL with parameters indicating an error.
The parameters look like the following:
?error=invalid_request&error_description=AADSTS90027%3a+We+are+unable+to+issue+tokens+from+this+API+version+on+the+MSA+tenant.+Please+contact+the+application+vendor+as+they+need+to+use+version+2.0+of+the+protocol+to+support+this.%0d%0aTrace+ID%3a+60c3dfca-739d-439a-94e3-05345df4ea00%0d%0aCorrelation+ID%3a+907818ee-d2f2-444e-acc8-745c102251fa%0d%0aTimestamp%3a+2021-04-26+05%3a33%3a02Z&admin_consent=True&state=80ffc4c9-e395-4d64-8b34-41531015a780#
We are using this endpoint URL:
https://login.microsoftonline.com/common/adminconsent
I don't see how this could be wrong.
I have searched for this error message but am having trouble finding an effective solution. Is there anything I can do to improve the situation?
I am integrating fitbit in iOS app, my issue is - after login with fitbit account.
I am getting code and with that code getting refresh token and access token by using http request, But when I refresh that refresh-token value by http request I am getting error.
Error is as below.
"Refresh token invalid or expired:"
If any anyone have any idea regarding this issue then kindly help me out.
Thanks
I'm currently working on an app that needs to integrate Vimeo. I'm therefore adapting my working OAuth2 client to allow authorization to Vimeo it's new beta API.
However, there are some things that are unclear to me, and the documentation is a bit vague on the matter.
Should I get the client authorized before authentication?
The user authentication url is https://api.vimeo.com/oauth/authorize, should I send a GET or POST request to this URL with the required parameters?
Should I send a basic authorization header (Authorization : basic base64(client_id:client_secret) along with authentication or should it be unauthenticated authorization header (Authorization : Bearer unauthenticated_access_token)?
Should I handle the authentication dialog through a UIWebView or through Safari?
Furthermore, I seem to get the error: { "error": "An unknown error has occured. Please let us know!"} when handling authentication through Safari. Does anyone have a clue on what actually went wrong or provide a way to find out? (Seems Vimeo improved their error displaying overnight ;))
The actual error I get is that the redirect_uri and client_id are missing, but I'm reasonably sure they get provided in the request body when doing a POST, or in the parameters when doing a GET. Any pointers?
Client authorization is not necessary to generate User authentication. Client authorization is only necessary to make unauthenticated api requests.
You don't make a request to api.vimeo.com/oauth/authorize, you send your user there. You should create a link, and put it on a page for your user to click. They will make a GET request to that endpoint, but it should not happen through your server.
Since your client is making a request to /oauth/authorize, there is no way you can define the headers. You will need to provide an authorization header to /oauth/access_token, and this should be Authorization : basic base64(client_id:client_secret)
We did fix a bug last night in our oauth error reporting :D. Sorry for the temporary confusion.
Without more information I can't really answer your error message. I'll add some comments, and then update this answer with more information.
I am using scribe 1.3.1.jar.
I have successfully authenticated user with twitter using this jar.
But I am facing problem while authenticating user with linkedin using the same jar.
I am getting this error while obtaining access Token. I have successfully get request token & verifier.But the problem creeps when i tried getting access Token & got following exception:
Response body is incorrect. Can't extract token and secret from this:
oauth_problem=signature_invalid&oauth_problem_advice=com.linkedin.security.auth.pub.LoginDeniedInvalidAuthTokenException%20while%20obtaining%20request%20token%20for%20%3APOST%26https%253A%252F%252Fapi.linkedin.com%252Fuas%252Foauth%252FaccessToken%26oauth_consumer_key%253Dxuk04eooznqu%2526oauth_nonce%253D2417349075%2526oauth_signature_method%253DHMAC-SHA1%2526oauth_timestamp%253D1365577634%2526oauth_token%253D7277829e-e121-4b76-b0f4-8f5e9e6c7be8%2526oauth_verifier%253D66312%2526oauth_version%253D1.0%0AOAU%3Axuk04eooznqu%7C7277829e-e121-4b76-b0f4-8f5e9e6c7be8%7C%2A01%7C%2A01%3A1365577634%3AlCqOvqH1tkJAtpGa58tnEhqwdRQ%3D
I feel really stuck in this.
Please Help!.
Take a look at this blog post: http://www.objectpartners.com/2012/04/03/linkedin-api-in-a-grails-application/
It shows how to use the OAuth plugin which uses the Scribe library. Hope that helps!
I am using google OAuth2.0 for LinkedIn integration in IOS. But I got 404 error when app try to get the accesstoken. Can you have a look at it and give me some guidance? Thanks in advance
I have tracked the request and have them below:
Generate the authorization code, the http request like below:
https://www.linkedin.com/uas/oauth2/authorization?client_id=dqabmvt35aee&redirect_uri=http%3A%2F%2Fwww.google.com%2FOAuthCallback&response_type=code&scope=r_emailaddress&state=DCEEFWF45453sdffef424
Then get the redirect URI like:
http://www.google.com/OAuthCallback?code=AQRnqUBueoz5jZqolVl5suiUQFnLExkmRQSOdndgFK59t4cKC4EjUm38zTbXjDvLwWItUrYrXnOt6KRxTz_SZ5m0Qq3t9rZHG1q-aqltb79m7ZJ5K2Y&state=DCEEFWF45453sdffef424
Do the post request for getting accessToken
https://www.linkedin.com/uas/oauth2/accessToken/
Request body like:
client_id=dqabmvt35aee
&client_secret=tlsAaUCZ5XtrTfHz
&code=AQRnqUBueoz5jZqolVl5suiUQFnLExkmRQSOdndgFK59t4cKC4EjUm38zTbXjDvLwWItUrYrXnOt6KRxTz_SZ5m0Qq3t9rZHG1qaqltb79m7ZJ5K2Y
&grant_type=authorization_code
&redirect_uri=http%3A%2F%2Fwww.google.com%2FOAuthCallback
And the got 404 error here.
Finally I figured it out by myself. What caused this issue is about the access token URL. I have the SLASH end of this URL which caused this issue. In google oauth 2.0 library, we should set the accesstoken url like "https://www.linkedin.com/uas/oauth2/accessToken", not should be "https://www.linkedin.com/uas/oauth2/accessToken/"