Activities of "gterdem"

Yes, you can try using TenantSettingValueProvider. Let us know if you come across any problems related to using it.

2022-05-18 01:01:27.895 +00:00 [ERR] Invalid redirect_uri: https://test1.test.schemasight.com/authentication/login-callback

AllowedRedirectUris":["https://test.schemasight.com/authentication/login-callback"]

Your database has https://test.schemasight.com/authentication/login-callback as RedirectUri for your application but it should be https://test1.test.schemasight.com/authentication/login-callback or vise-versa.

Update your database with the correct redirectUri of the application.

I couldn't reproduce the error.

Did you try creating a new form after updating to 5.2.2 and add questions / answers to newly created form?

Your swagger UI configuration doesn't seem correct.

https://medistat.co.za/medistatapi/swagger/swagger/v1/swagger.json seems to have extra /swagger https://medistat.co.za/medistatapi/swagger/v1/swagger.json works

Can you explain more of your intentions? Do you already have a separate identity server project with your business code in it and you decided not to use a separate IdentityServer? Or is it about the login page only that you want to host login pages in your angular instead of redirecting back to IdentityServer?

1. Do you have any errors when you check developer console (F12) of the browser?
2. Is your project template Blazor WebAssemby non-tiered? What is your exact template version?
3. Do you have front-channel logout altered or any identityserver-related data changes?

Are you guys looking into it or Just joking with me?

Hello,

It could be shorter if you would share the link (/authentication/logged-out) in the screenshot.

After IdentityServer single logout action, the user is redirected back to Blazor application. This URL (/authentication/logged-out) is handled by the Microsoft OIDC Provider and it is not related to ABP.

When we investigate more about the Microsoft.AspNetCore.Components.WebAssembly.Authentication, we have limited options to modify the remote views.

Instead of modifying the remote view, you can set the authentication/logged-out path to index page should redirect you back to login page since the index.razor is supposed to be authorized already.

Update the ConfigureAuthentication method of BlazorModule as follows:

private static void ConfigureAuthentication(WebAssemblyHostBuilder builder)
{
    builder.Services.AddOidcAuthentication(options =>
    {
        builder.Configuration.Bind("AuthServer", options.ProviderOptions);
        options.UserOptions.RoleClaim = JwtClaimTypes.Role;
        options.AuthenticationPaths.LogOutSucceededPath = "/"; // This will redirect the application to "/" instead of logged-out page which will trigger authentication again
        options.ProviderOptions.DefaultScopes.Add("MyApp");
        options.ProviderOptions.DefaultScopes.Add("role");
        options.ProviderOptions.DefaultScopes.Add("email");
        options.ProviderOptions.DefaultScopes.Add("phone");
    });
}

<br> You can see Microsoft documentation of Blazor Web Assembly for additional scenarios for more information.

Please share the IdentityServer logs. It should be under Logs folder with the name logs.txt.

Did you try the non-separate identityserver template?

I examined the Forms module but I couldn't find any dependencies for build tools, are you able to confirm if you are not using any build tools for bundling or compiling the Vue code (.js component files)? https://v2.vuejs.org/v2/guide/deployment.html#Without-Build-Tools

Yes, we do not use any build tools. It is embedded in .cshtml files as html.

Also, since Vue 3 is backwards compatible with Vue 2, do you think I can replace the @abp/vue standard package (which uses Vue 2) with the Vue 3 official package (since I want to use Vue 3 in my application), and still have the ABP Forms module still working?

You can surely try it and let us know the results and/or any problems you come across so that we can try to help you solve them.

If not, what's the likelihood of the Forms module upgrading to Vue 3 within the next 2 years?

We don't have plans for updating it for now. But if you think we should, please share it at support feature request.

Can you check your running containers with docker ps -a command? Do you see the redis is up and running? Can you share the redis container logs?