invalid_client error - Microsoft azure V2 endpoint - oauth-2.0

i am using V2 endpoint as explained here https://azure.microsoft.com/en-us/documentation/articles/active-directory-v2-scopes/ to connect to Microsoft Login. I am getting invalid client error after i sign in. in fiddler i see following error , can someone please help me.
AADSTS70002: Error validating credentials. AADSTS50012: Authentication failed
Trace ID: c62c9e93-f7c9-43fe-b5eb-4a6f9dfe6be0
Correlation ID: c14f259c-3e91-4e51-9f82-8feabd35bf5d
Timestamp: 2016-07-22 21:04:19Z

I was receiving the same error and just removing the last forward slash worked for me. Instead of
https://myapp.com/
I used this
https://myapp.com
and invalid_client error went away. It seems the redirect URLs have to exactly match as configured in AZURE AD.

Related

Blackberry UEM REST API 401 Unauthorised error

Unable to perform any authorized API calls using the Blackberry UEM REST API service. I'm running a trial cloud instance of Blackbery UEM and calls to "ping" and "authorization" works. However, after obtaining the authorization code, using it on any REST calls fails with the error 401 Unauthorized.
The credential used is of an administrator with the "Security Administrator" role which has full permission. I have also tried the above in postman and also the sample PowerShell command, but the results are the same.
Does anyone know what's going on wrong here? Am I missing any configuration? I am going a bit crazy... Thanks.
if you get a 401 error, its almost always an issue with the account/authorization your using.
Since your connecting to the cloud instance of UEM, it ONLY support OAuth authentication. For this to work, you will need an token, not an authorization code. Here is a devblog.blackberry.com entry on the steps: https://devblog.blackberry.com/en/2020/07/new-authentication-option-for-rest-apis-oauth.
Give that a try instead.

Oauth LinkedIn Authentication error (System.HttpResponse[Status=Forbidden, StatusCode=403])

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

How to debug keyrock

I have succesfully used the shared keyrock from filab to let my on web application to authentificate users, using oauth.
When I tried it with a second application, I get an error from FILAB web page: "Bad Request"
The error occurs after the users logs in.
Is there a way to get additional information, what was wrong with the request?
I'm guessing you are using the "authorization code grant" flow defined by the OAuth2 standard and supported by Keyrock. In that scenario, you need to provide three parameters when building the authentication URL:
response_type must be code (or token when using the "implicit grant" flow), otherwise IdM will return an unsupported_response_type error.
If the client_id exists, but the redirect_url doesn't match the one provided when creating the application, then a bad request error will be raised. This error can be raised if the client_id is wrong, if the redirect_url is wrong or if both are wrong. This is your case.
If the client_id app doesn't exist, the IdM will return a 404 error page.
If any of these parameters are missing in the request, the IdM will raise an invalid_request error.
Except for the error 404, Keyrock seems to follow the OAuth2 protocol.

authority labs API callback

I am using Authority labs API in my rails application for ranking service. I am getting connection refused(2) error when I check in API error list.It shows the error type as Callback Error. Please guide me to fix this.

OAuth Unauthorized Client Error

Working on my Google Glassware and everything seemed to be going fine. I tried loading it up the other day after a while of not working on it and had an OAuth error. I tried refreshing the key and even starting a new project. The Error I got has atleast changed I am now getting -
An error occurred: Error refreshing the OAuth2 token, message: '{ "error" : "unauthorized_client" }'
The code is pretty much completely based off of the PHP Quick Start. This happens when I try and authorize the app with my account. I know my information is correct for the config.php file. Any suggestions?
I think in this case , it is possible that Authorization server has not allowed to access Authorization grant type
{error: 'unauthorized client'} may be related to Authorization server settings
Grant_types it has allowed.
Reference: http://tools.ietf.org/id/draft-ietf-oauth-v2-12.html#token-errors

Resources