What about impersonation for for Blazor WASM?
- ABP Framework version: v4.4
- UI type:Blazor
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace:
- Steps to reproduce the issue:"
When will user impersonation same as in aspnetzero be available for Blazor WASM devs?
This is a really critical support tool for SaaS.
@Albert - Thanks. The first issue is having to redirect from the website that is created by the app, then to the login page. This also happens when the user logs off. It goes to the website (we dont use that), and then redirects to the login page.
We want users to be able to go straight to the login page.
- ABP Framework version: v4.3.3
- UI type: Blazor WASM
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): yes / no
- Exception message and stack trace:
- Steps to reproduce the issue:"
The speed to load the login screen, and then once logged in to load the WASM app is very slow.
Load login page - Click a URL eg login.myapp.com to open at the login page and measure speed. This should be 1sec max, it's a simple form, but has to do crazy redirects to just get to the login page. We need to fix that so it just gores straight to the login page.
Load app - Then enter credenttials, click login, and measure speed to load app. This is extremely slow.
I know there have been a few go arounds on this with other issues and there are some Blazor issues with app load, but the first one should be trivial to resolve so it just goes straight to the Login screen.
when will v4.3 patch be released and what is fixed for commercial over what shown in github?
v4.3.2 comes Fiday.
@Albert - Thanks for the date on v4.3.2, where can we see what will be fixed/released in the Commercial version?
Github only shows what is in the open source version.
when will v4.3 patch be released and what is fixed for commercial over what shown in github?
The main problem is the information in the error message is not helpful.
so that is the first thing to resolve.
We do not want to download and edit source as that will then be a problem when we have to upgrade eg 4.3 patch.
@liangshiwei Thanks, we'll try that I really hope you can get this framework faster, we would have to change lots of things to migrate back to a Server. I already discussed that in a different question and Alpers said we had to create a brandnew tenmplate and t5hem migrate the whole app piece by piece over...
- ABP Framework version: v4.3
- UI type: Blazor
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): yes / no
- Exception message and stack trace:
- Steps to reproduce the issue: example below where user connection is lost and what they need to do is login again.
How can we improve the error messages like this one, which is not helpful for a user, without having to edit the source because that breaks the ability to easily upgrade.
