-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any plan to support new version of Microsoft.Identity.Client? #15
Comments
This is a silly blocker, possibly on the part of Microsoft.Identity.Web for changing the API. For anyone else that encounters this issue and if you're using |
I assume this is why I'm getting
|
Hello, we'll be adding support in a future version |
@lsannicolas that was fast - support is already complete? Hmm, I don't see any PRs that mention this? |
We haven't created the PR yet. I'll reopen the issue and link the pr once that is posted |
When will the support for 4.55 version of Microsoft.Identity.Client be added? |
We’re hoping to add it in the next version release, but there’s no date set for that just yet. I can update here once we get a better idea of a timeline |
@rudiv - I'm guessing you took a dependency on MSAL 4.53 for Managed Identity APIs? but the APIs were marked as experimental and we indeed changed them based on partner feedback To everyone reading this, you can either downgrade the version CC @gladjohn |
The new release v2.0.0 uses the latest Microsoft.Identity.Client package. Please give it a try and let us know if you still see any issues. |
since my project used 4.55 version of Microsoft.Identity.Client, there is some dependency problem about can't resolve right method. And as I checked, the method in it ManagedIdentityApplicationBuilder.Create has changed (they changed the method's parameter, but do not support the old one), does not support use a string parameter directly.
It's OK for me, I can downgrade my package reference to 4.53 resolve it, but is there any plan for it?
The text was updated successfully, but these errors were encountered: