Closed knobel-dk closed 2 weeks ago
@knobel-dk Thank you for upgrading to the latest SDK and reaching out. Yes, there are some expected breaking changes between the RC and the stable versions.
For your scenario, you'll need to use the AuthorizationCodeContext
since you're using the OAuth 2.0 authorization code flow to authenticate. See this for more.
The latest SDK is able to do the token request for you when given an authorization code. It also refreshes this access token when needed and caches it in memory. You can also choose to pass in an already retrieved access token to the GraphServiceClient
- more
We also provide an Upgrade Guide with more samples and features.
Feel free to reach out in case of any further challenges.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
The repo has very few examples and no upgrade guide. A few issues here wonder where
Microsoft\Graph\Graph
went.I tried figuring out myself and am pretty sure that this is a breaking change, if not a bug or undocumented behavior.
This code worked on
2.0-RC4
:Then I upgraded to 2.14 and tried this (kindly look at the two comments):
It gives
Assertion failed signature validation
Here is the controller consuming `` for both versions: