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
Make the presence of Identity UI more explicit in the starter template or documentation #5837
Comments
See this discussion aspnet/Identity#1825 |
@HaoK Can we address this with comments in 3.0? |
@ryanbrandenburg Apparently you are Mr Templates now, so can you add a suitable comment? |
I can certainly see how that might be confusing. I think it's unlikely to get noticed in the documentation. @danroth27 do you think just a comment above Also CC @javiercn who does all the Identity work. |
I'm fine with that, but it's really @blowdart's call. |
I already said a comment would do. |
Comment should read as /// .addDefaultUI embeds web pages to support login, logout and other identity functions without having to create pages in your project. |
We can close this now as the default experience for templates already includes .AddIdentityUI with the framework version. |
I just started looking into authentication for Razor pages, and I found the experience with the starter template to be very confusing. I saw that there's already a couple of GitHub issues related to this, but I think the experience still needs some work. This post on StackOverflow exemplifies exactly what I went through earlier today. I wanted to share some feedback.
The idea of packaging UI in a library, especially UI as involved as authentication, is intriguing. But it hasn't been done in an ASP.net template before (that I'm aware of), so when you create a starter project and you see register and login forms that appear nowhere in your project files, it's quite disorienting. Like the poster in the StackOverflow question, I searched for that string to find the source, but found nothing. Other pages like the landing page, About, etc. do exist, but the account pages are there as if by magic.
The source of the UI, the AddDefaultIdentity statement in Startup.cs, gives no hints that it comes with UI included. The previous method of including AddDefaultUI in your service configuration at least had UI in the name.
Mentioning the existence of Identity UI in the documentation or somewhere in the template would help. I'm not sure what the main entry point to Razor pages is as far as documentation goes, but I was using this article: Introduction to Identity on ASP.NET Core. That might be a good place for a heads up about this new thing called Identity UI, which is the component that causing those authentication forms to appear. But you may be aware of a better place to put it.
The text was updated successfully, but these errors were encountered: