Login customisation

[Viktor-Mihalenko]

I am using example 7 and want to allow registration only via the “Sign up a new tenant” option, not through the standard ASP.NET library.
Additionally, I would like to adjust the standard registration routine so that, when people try to access it, they are always redirected to the login page, and I would also like to hide the register button on the login page. Since the login and register pages were not present in the project, I added them using the following command:

dotnet aspnet-codegenerator identity -dc ApplicationDbContext --files "Account.Register;Account.Login;Account.ResetPassword"

The issue I’m facing now is that no matter what I modify, the application still doesn’t use the pages I customized. Instead, it keeps using the default ones that were already in place. How can I ensure that my application uses my pages and follows my custom routines

[JonPSmith]

Hi @Viktor-Mihalenko,

I have never used the dotnet aspnet-codegenerator so I can't comment on that.

I should say that the AuthP library doesn't have any ASP.NET Core frontend features, e.g. pages, logins, etc. apart from AuthP code in "Sign up for a new tenant" and the "Invite new user feature" features. Both of these features uses AuthP's Add New User adapter to work with different types of logins.

You might find the article Three ways to securely add new users to an application using the AuthP library which shows different ways for a new user can register to an AuthP app.

I would also suggest you try things out on Example3 as its the simplest multi-tenant applications first.