Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Azure AD v2.0 not work as expected

See original GitHub issue

According to the document, the endpoint for auth and token should be:

https://login.microsoftonline.com/{tenant}/oauth2/v2.0/authorize
https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token

https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow

Here is a reference implementation: https://github.com/microsoftgraph/console-java-connect-sample/blob/master/src/main/java/com/microsoft/graphsample/connect/MicrosoftAzureAD20Api.java

Issue Analytics

State:
Created 5 years ago
Comments:12 (5 by maintainers)

Top GitHub Comments

2reactions

kullfarcommented, Feb 8, 2019

release 6.3.0 is on the maven central already

0reactions

oscarariascommented, Feb 7, 2019

Awesome! Big thx! 👍

Top Results From Across the Web

Azure AD authentication & authorization error codes

Azure AD Authentication and authorization error codes ... This is a common error that's expected when a user is unauthenticated and has not...

Azure AD PowerShell v2 cmdlets not working, e.g. Get ...

If I run Install-Module AzureADPreview, then run Connect-AzureAD, it loads AzureAD module and the Preview cmdlets can't be found... I can't run Preview...

I am unable to get access token from the microsoft active ...

I need to call https://login.microsoftonline.com/{tenant}/oauth2/v2.0/authorize to get the code that is necessary for getting the token. Then I ...

Troubleshoot user update issues with HR provisioning

Null and empty values not processed as expected ; Issue, You have successfully configured the inbound provisioning app. You are getting null or ......

Azure AD returns claims in a different format than expected

I think the difference is between version 1 and version 2 of the claims object getting returned. I have looked through the Azure...