You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I have just tested this and it seems to work correctly for me. One issue I can see is that Microsoft Graph doesn't offer v1.6 endpoint, you should be using v1.0, which version of the library are you using - dev-master, v1.1.1 or v2.0.0.x-dev?
Update: I have actually tried with dev-master and I am running into the same issue. However with v2.0.0.x-dev everything works fine. I will look into this further.
Update 2: Discovered the issue - it is a coding flaw (
// The id_token is unsigned (coming from v1.0 endpoint) - https://msdn.microsoft.com/en-us/library/azure/dn645542.aspx
), will release v1.2.0 very soon which also includes the fix. The issue lies in the fact that the id_token is not signed in v1 flow and it appears that access_token signature is "weird" in case of using https://graph.microsoft.com/ resource.
Great to know!! I'll make the modifications on the endpoint version that you suggested, and wait for the next release. Meanwhile I'll check it with v2.0.0.x-dev version.
Hi,
When I try to use any Graph resource I get following error:
OpenSSL unable to verify data: error:04091068:rsa routines:INT_RSA_VERIFY:bad signature
the resource URL that I'm using is https://graph.microsoft.com/
I set the provider configuration as is explained in the documentation, but keeps failing.
Here is the code that I'm using:
If I use https://graph.windows.net as the resource, the token is correctly validated.
Thanks in advance!
The text was updated successfully, but these errors were encountered: