Skip to content

[Blazor] Provide redirect to login component in Microsoft.AspNetCore.Authorization #18979

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

Closed
javiercn opened this issue Feb 12, 2020 · 3 comments
Labels
affected-few This issue impacts only small number of 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-builtin-components Features related to the built in components we ship or could ship in the future help wanted Up for grabs. We would accept a PR to help resolve this issue severity-minor This label is used by an internal tool
Milestone

Comments

@javiercn
Copy link
Member

javiercn commented Feb 12, 2020

We plan to include it as part of the templates for auth in Blazor wasm, but we should have one out of the box in Microsoft.AspNetCore.Components.Authorization given that this is not wasm specific.

@javiercn javiercn added the area-blazor Includes: Blazor, Razor Components label Feb 12, 2020
@javiercn javiercn added this to the Next sprint planning milestone Feb 12, 2020
@javiercn javiercn added the enhancement This issue represents an ask for new feature or an enhancement to an existing one label Feb 12, 2020
@ryanelian
Copy link

Would this feature only limited in Blazor WASM?

I made a past issue where this feature is also crucial in server-side Blazor using OpenID Connect: (it is marked as Discussion unfortunately)

#13709

There are numerous other people in that thread who also requested such feature to be implemented.

@captainsafia captainsafia added the help wanted Up for grabs. We would accept a PR to help resolve this issue label Sep 9, 2020
@javiercn javiercn added affected-few This issue impacts only small number of customers severity-minor This label is used by an internal tool labels Oct 9, 2020 — with ASP.NET Core Issue Ranking
@ghost
Copy link

ghost commented Oct 9, 2020

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.

@javiercn javiercn added the feature-blazor-builtin-components Features related to the built in components we ship or could ship in the future label Apr 19, 2021
@mkArtakMSFT
Copy link
Contributor

Hi. Thanks for contacting us.
We're closing this issue as there was not much community interest in this ask for quite a while now.
You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.

@mkArtakMSFT mkArtakMSFT closed this as not planned Won't fix, can't repro, duplicate, stale Oct 19, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Nov 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affected-few This issue impacts only small number of 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-builtin-components Features related to the built in components we ship or could ship in the future help wanted Up for grabs. We would accept a PR to help resolve this issue severity-minor This label is used by an internal tool
Projects
None yet
Development

No branches or pull requests

4 participants