Skip to content
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

Blazor Webassembly AAD and AAD B2C support improvements #27549

Closed
7 tasks
Tracked by #26364
javiercn opened this issue Nov 5, 2020 · 6 comments
Closed
7 tasks
Tracked by #26364

Blazor Webassembly AAD and AAD B2C support improvements #27549

javiercn opened this issue Nov 5, 2020 · 6 comments
Labels
affected-medium This issue impacts approximately half of our customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly feature-blazor-wasm-auth severity-blocking This label is used by an internal tool Theme: meeting developer expectations
Milestone

Comments

@javiercn
Copy link
Member

javiercn commented Nov 5, 2020

Here are some of the things we don't support we have received feedback about, and we could consider doing on the 6.0 timeframe.

  • Support for reset password flow in Azure AD B2C.
  • Login with Identity Providers (option to skip silent token acquisition/login)
  • Support for incremental consent.
    • Enable requesting scopes incrementally when the app needs them instead of requesting all during startup.
  • Support for login hint
  • Support for prompt options
  • Silent sign on
  • Support for conditional access
@ghost
Copy link

ghost commented Nov 5, 2020

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@mkArtakMSFT mkArtakMSFT added the area-identity Includes: Identity and providers label Nov 5, 2020
@mkArtakMSFT mkArtakMSFT added affected-medium This issue impacts approximately half of our customers enhancement This issue represents an ask for new feature or an enhancement to an existing one severity-blocking This label is used by an internal tool labels Nov 12, 2020 — with ASP.NET Core Issue Ranking
@AlbertoPa
Copy link

Any chance the password reset workflow is addressed for 5.x?
In the current status, for Blazor Webassembly, there isn't a clean approach to have this basic functionality without writing a good amount of user code.

@chrislangston
Copy link

Any chance the password reset workflow is addressed for 5.x?
In the current status, for Blazor Webassembly, there isn't a clean approach to have this basic functionality without writing a good amount of user code.

We also face issue with being able to use Blazor Web Assembly with AD B2C for our clients since we have not been able to figure out how to handle the redirect back to the client after they have selected the option that they have forgotten their password.

Seeing an example of how we can intercept this error in the query string and then handle the redirect approprately would be helpful.

https://localhost:5001/authentication/login-callback#error=access_denied&error_description=AADB2C90118%3a+The+user+has+forgotten+their+password.%0d%0aCorrelation+ID%3a+6e6935b7-b602-4228-b658-1c3e942fcc57%0d%0aTimestamp%3a+2020-11-25+18%3a56%3a40Z%0d%0a&state={SOME STATE VALUE}

@ghost
Copy link

ghost commented Jul 20, 2021

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@AlbertoPa
Copy link

AlbertoPa commented Feb 8, 2022

In reference to my comment above, password reset is now managed with the self-sevice password reset process, directly through AD B2C, which works fine.

However, profile editing and other user's flows available by default in AD B2C do not have support, so it would be nice to have those supported out of the box (a way to capture the callback in Blazor would be needed).

Thanks!

@javiercn
Copy link
Member Author

All these are covered by #42580

@javiercn javiercn modified the milestones: Backlog, 7.0-rc1 Aug 23, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Sep 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affected-medium This issue impacts approximately half of our customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly feature-blazor-wasm-auth severity-blocking This label is used by an internal tool Theme: meeting developer expectations
Projects
None yet
Development

No branches or pull requests

4 participants