What exactly do you want to do?
Want to customize the UI side? See: https://community.abp.io/posts/how-to-customize-the-login-page-for-mvc-razor-page-applications-9a40f3cd
Want to customize the sign-in manager? See: https://community.abp.io/posts/how-to-customize-the-signin-manager-3e858753
Here is a list of other resources related to customization: https://support.abp.io/QA/Questions/160/How-to-customize-an-ABP-project
Hello, I have created an issue on the subject. See: https://github.com/abpframework/abp/issues/16130
As you said for PRO packages, it first looks at nuget.org and then when it returns null, it looks at nuget.abp.io. This both causes performance loss and creates the perception that there is an error because nuget.org returns 404.
I'm closing this topic because it will be followed up with this issue.
Closing the issue. Feel free to re-open or create a new issue if you have further questions.
You're welcome. Have a nice day
Closing the issue. Feel free to re-open or create a new issue if you have further questions 😄
The problem is that you have installed Hangfire in ConfigurateurClient.Admin.HttpApi.Host. If you want to use Hangfire in this project, you should edit ConfigureAuthentication similar to ConfigurateurClient.Admin.Blazor, but I don't recommend it. You don't need to open ConfigurateurClient.Admin.HttpApi.Host outside, it can stay internal. Users with ConfigurateurClient.Admin.Blazor admin privileges can access as the UI allows, but they don't need to access ConfigurateurClient.Admin.HttpApi.Host so you don't need to open its URL outside.
As a result, if you want to solve the problem with the least effort and with a more accurate method, you can solve the problem by moving similar codes to ConfigurateurClient.Admin.Blazor. I tried it works, you can see the screenshot below.
The problem should be solved, can you try again?
Got it, you can grant access to this GitHub account.
I am very happy with the information you have given because I understand the problem. But we need to verify, so can you visit the /account/login page and try again after login?
I understand, but you're logged in, right? You can see your account information, or if you are logged in as an admin user, you can visit the page where you can see the list of all users and so on, right? If so, I might need to take a closer look at your project. It's hard to say anything directly.
Yes, because the CurrentUser service is resolved from RequestServices in IsLoggedIn method.
See: https://github.com/abpframework/abp/blob/ba6ded35524cd4f743f263f33ac37cbc8f238fcd/framework/src/Volo.Abp.HangFire/Volo/Abp/Hangfire/AbpHangfireAuthorizationFilter.cs#L38-L45