-
Notifications
You must be signed in to change notification settings - Fork 328
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
[Feature Request] Deprecate Old WAM #3447
Comments
@jmprieur - I was thinking we do this as part of 4.x ? Here's how I see this done:
ALTERNATIVE:
It's true that CC @pmaytak @trwalke @neha-bhargava @sameerkapps for suggestions |
@bgavrilMS : I guess I would need to see the before / after in term of API / DevEx to fully understand |
do we have a final plan on the deprecation of the old broker? are we doing the alternative approach? "Deprecate MIcrosot.Identity.Client.Broker and move all functionality to Microsoft.Identity.Client.Desktop. Should be a drop-in replacement, but we cannot gurantee that the exact scenarios will work." Or "Deprecate Microsoft.Identity.Client.Desktop package via nuget message which recommends use of MIcrosot.Identity.Client.Broker package instead." and GA the new broker. But the older broker (Desktop) can be used for WebView2 and UWP @SameerK-MSFT @neha-bhargava @trwalke @pmaytak other ideas? |
@SameerK-MSFT assigning this to you since you are working on finalizing the design |
Adding this to in-progress to track the deprecation of the old broker and for naming the new APIs |
Is your feature request related to a problem? Please describe.
Explore options on how to deprecate the old WAM broker
Describe the solution you'd like
need to explore possible solutions
Describe alternatives you've considered
none
Additional context
This will make the new broker the only option in MSAL .Net for WAM
The text was updated successfully, but these errors were encountered: