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.
Hi we figured out that our Blazor WASM issue with this is still an issue (we are on 7.0.1 separte Identity)
https://support.abp.io/QA/Questions/4071/401-error-when-trying-to-download-GDPR-information
We still get a 401 error and have no idea what we need to do/add to gett it to work (if there is somethint we can do on our side).
Btw commenting here because our issue is locked..
I have unlocked the question and written an answer please check it.
Hi @Sturla, I have seen your comment in our discord channel and created a new 7.0.1 app-pro template to check is there any problem on GDPR module, but it works as expected like in the gif below:
I remember that you got this problem on your application and then you noticed it was related to your CDN and worked when you cleared:
Your problem might be related to that, since I could not reproduce your problem on a newly created app-pro template (blazor - separated auth server - 7.0.1). Also, please check for redis is up and running, because it also gives 401 if could not require a mutex lock.
Best Regards.
Hi, as @liangshiwei mentioned, we fixed the problem on our NuGet Server and refunded your ticket, thanks for your understanding. I close the question, if it still persists for you, please don't hesitate to reopen it.
Best Regards.
Hi, as @liangshiwei mentioned, we fixed the problem on our NuGet Server and refunded your ticket, thanks for your understanding. I close the question, if it still persists for you, please don't hesitate to reopen it.
Best Regards.