We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given the following boilerplate: dotnet new react -o <output_directory_name> -au Individual
Is there a way to modify the styling of the account pages? (such as login or register) For example: https://localhost:5001/Identity/Account/Register?returnUrl=/authentication/login
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered:
You can follow the steps in https://docs.microsoft.com/en-us/aspnet/core/security/authentication/scaffold-identity?view=aspnetcore-2.2&tabs=visual-studio to modify the look and feel of the included Identity UI
Sorry, something went wrong.
Hi @MarkMurphy37 ... Looks like your question has been answered. I'll close now.
Thanks! I'll give this a shot. For reference, I'm running .net core 3.0 preview with React SPA auth.
It may be worth including a link on this page: https://docs.microsoft.com/en-us/aspnet/core/security/authentication/identity-api-authorization?view=aspnetcore-3.0 because it's not apparent after spinning up the project that you can alter those pages.
Yes, great idea. I'll do that right now.
guardrex
Successfully merging a pull request may close this issue.
Given the following boilerplate: dotnet new react -o <output_directory_name> -au Individual
Is there a way to modify the styling of the account pages? (such as login or register)
For example: https://localhost:5001/Identity/Account/Register?returnUrl=/authentication/login
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: