Can you share the following information?
I fixed the problem by implementing another authentication schema, so in that way i can challenge the user to authenticate and when it is done i can sign in the user and redirect the user to the page.
Great to hear that you fixed the problem.
I didn't understand how i can pass the authorization header while i am redirecting the user from angular. Is there any sample code how to do that? I would be happy if you can share it.
Actually, I was just clarifying the flow in a normal situation. For your requirement, creating a new authentication scheme and challenging to login with redirect uri as /hangfire is a good approach I think. And i don't have any alternative to that approach for now.
Hello again, Thanks for the explanation, can i ask how can i do the same for hangfire dashboard? If i write a mvc controller action, how can i redirect the user to auth server log in page and then redirect to hangfire dashboard?
Hi, you can do this easily by redirecting to auth server and specifying the ReturnUrl as /hangfire (https://localhost:5000/Account/Login?ReturnUrl=https://localhost:5001/hangfire), however, even if you do that, you should pass the authorization header from auth server to your host application somehow, so a simple redirection would not be enough.
Ideally, you need to authenticate via your client application, retrieve the token, and use it in the authorization header in the subsequent calls that you'll make to the host application.
Hi, this is the expected behavior. Because, when you authorize through Swagger, in every request that you made through Swagger, an authorization header will be passed with the bearer token (ABP intercepts the call and pass the token, in the js side), and that makes you authorized.
However, if you navigate to the /hangfire page, you will see 401 status code, because there is not any authorization header in the request headers. You should set the authorization header with the bearer token in your request by yourself.
It seems that the template for Blazor Server doesn't put the Authority app setting in the AuthServer sections of the appsettings.json.
Thanks for reporting, I will check it.
Hi, we are actively working on LeptonX Theme and our focus on it. We are adding new features, enhancements, and fixes to it. On the other hand, the Lepton Theme is also our product, we continue maintaining it and fixing bugs. But, as you may understand since our active focus is on LeptonX Theme, it might be a better choice for you to migrate to. Because then you can get better help from us since our active focus is on LeptonX Theme and currently maintaining it. Also, if there is a bug at any point, it's most likely to be noticed in LeptonX Theme first.
Migrating to LeptonX Theme is pretty straightforward. Please check the documentation and give it a try: https://docs.abp.io/en/commercial/latest/themes/lepton-x/blazor?UI=Blazor
If you are not planning to migrate your theme, it's completely understandable, and you don't need to worry about it. We will help you if you face any problems with the old Lepton Theme. We don't have any certain date to end support for Lepton Theme. But please note we are not considering adding any new feature to Lepton Theme.
I close the question since your problem is fixed now. (it was related to CDN not being up to date after the CDN cache got flushed it was fixed.)
Thank you for your answer but I would like to expand my question. For blob provider, I must to add some package(Google.Cloud.Storage.V1) from nuget. Would it be correct to add these packages to this layer? I am hesitant as to whether it would be correct to add these packages to this layer.
It would be wrong to add the package to your domain layer. The domain layer should be independent of external dependencies (you can change your mind and want to use another blob provider in the future for example). You can define interfaces for your blob operations and create an infrastructure layer for Google.Cloud.Storage.V1 and implement your interface in this layer. Then, your host project can depend on this infrastructure layer.
thank you. Have you considered MySQL? If so, I would like to know why you excluded MySQL.
The license cost for MS-SQL on Azure was significantly higher than PostgreSQL. This is also valid for MySQL. Therefore, after conducting a cost-benefit analysis, we migrated our database to PostgreSQL to save costs. Also, it has more features and good scalability than MySQL, as far as I see.
OK looks like this works fine locally
What could that mean? Everything else is working with authentication.. What can I check?
Can you share logs with me? I could not reproduce the problem, it might be the CDN cache as you stated before. Also, check redis is up and running, 401 error is also given if the redis is not running.