Activities of "dhill"

• ABP Framework version: v8.2.2
• UI Type: Blazor Server
• Database System: EF Core

We need to implement IDataFilter to apply a filter against EmployeeId where a claim of EmployeeId has a value matching records on the table.

Trying to apply the documentation in the wiki has been difficult as some of the steps seem to be summarized.

Can you provide guidance on how to implement this feature?

• ABP Framework version: v8.2.1
• UI Type: Blazor Web App
• Database System: EF Core
• Exception message and full stack trace:
• Steps to reproduce the issue:

The search box is missing from linked accounts.

When user login and logout of the application, and attempt to login as a tenant, user cannot see the "Login with this tenant" element under the action button

• ABP Framework version: v8.2.1
• UI Type: Blazor Web App
• Database System: EF Core
• Exception message and full stack trace:
• Steps to reproduce the issue:

Steps to reproduce:

1. Log in as an admin user
2. Go to "Saas" under Administration
3. Select "Tenants" under Saas
4. Click on the Action button for Greethem
5. Select the "Log in with this tenant" element
6. Click on the profile icon on the tenant page
7. Click on the Logout (To log out as tenant and admin user)
8. Enter the credentials again (as Admin)
9. Go to "Saas" under Administration
10. Select "Tenants" under Saas
11. Click on the Action button for Greethem
12. Check if the user can see the "Log in with this tenant" element

Expected: Users should be able to log in as tenants no matter how many times they log in and out of the application

Actual: Users cannot log in as tenants the second time

Attached is the video for reference (in the attachments) https://1drv.ms/v/s!AseK7NI9P0MAgc5WgkCbI4qhQYVOjA?e=Sd1cFo

• ABP Framework version: v8.2.1
• UI Type: Blazor Web App
• Database System: EF Core
• Exception message and full stack trace:
• Steps to reproduce the issue:

When users log out of the tenant account, they are not redirected to the admin account as before. Currently, the user is also logged out of the admin account.

Attached is the video for reference (in the attachments) https://1drv.ms/v/s!AseK7NI9P0MAgc5Y6uPnBLmclDoRhQ?e=MJKijc

• ABP Framework version: v8.2.1
• UI Type: Blazor Web App
• Database System: EF Core
• Exception message and full stack trace:
• Steps to reproduce the issue:

Steps to reproduce:

• Log in as an admin user
• Go to "Saas" under Administration
• Select "Tenants" under Saas
• Click on the Action button for Greethem
• Select the "Log in with this tenant" element
• Click on the profile icon on the tenant page
• Click on the Logout (To log out as tenant and admin user)
• Enter the credentials again (as Admin)
• Go to "Saas" under Administration
• Select "Tenants" under Saas
• Click on the Action button for Greethem
• Check if the user can see the "Log in with this tenant" element

Expected: Users should be able to log in as tenants no matter how many times they log in and out of the application

Actual: Users cannot log in as tenants the second time

Attached is the video for reference https://1drv.ms/v/s!AseK7NI9P0MAgc5WgkCbI4qhQYVOjA?e=Sd1cFo

• ABP Framework version: v8.2.1
• UI Type: Blazor Web App
• Database System: EF Core
• Exception message and full stack trace:
• Steps to reproduce the issue:

When user uses linked account to login to admin tenant from regular tenant the application crashes and logs out

Steps to reproduce:

• Log in as an admin user for a regular tenant
• Click on the profile icon of the user
• Click Linked accounts menu item
• Click actions next to admin tenant (user name shows no \ character)
• Select the "Log in with this tenant" element
• Application immediately logs out and redirects to \Dashboard
• User will be unable to login until cookies are cleared and the browser is re-opened

Expected: Users should be able to login as Tenants and use linked accounts into the admin tenant as many times as they wish.

Actual: Users cannot see the login to admin Tenant from regular Tenant without getting immediately logged out

Admin --> Identity Management --> Users --> Claims : Error when click on "Add claim"

Please see below screenshot.

• ABP Framework version: v8.2.1
• UI Type: Blazor Web App
• Database System: EF Core
• Exception message and full stack trace:
• Steps to reproduce the issue:

• ABP Framework version: v8.2.0
• UI Type: Blazor Web App
• Database System: EF Core
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Steps to reproduce the issue:

Subdomain tenant mapping is not working correctly after converting a Blazor Server to Blazor Web App.

Behavior Initially a user can login to the tenant as normal but after a couple minutes the session will force a logout.

Partial Console Logs:

dotnet.runtime.8.0.7.3bvrr6lyon.js:3  warn: Volo.Abp.IdentityModel.IdentityModelAuthenticationService[0]
      Could not find IdentityClientConfiguration for AbpMvcClient. Either define a configuration for AbpMvcClient or set a default configuration.
(anonymous) @ dotnet.runtime.8.0.7.3bvrr6lyon.js:3
dotnet.runtime.8.0.7.3bvrr6lyon.js:3 info: System.Net.Http.HttpClient.AbpMvcClient.LogicalHandler[100]
      Start processing HTTP request GET https://redacted.com/api/abp/application-configuration?IncludeLocalizationResources=False&api-version=1.0
dotnet.runtime.8.0.7.3bvrr6lyon.js:3 info: System.Net.Http.HttpClient.AbpMvcClient.ClientHandler[100]
      Sending HTTP request GET https://redacted.com/api/abp/application-configuration?IncludeLocalizationResources=False&api-version=1.0
dotnet.runtime.8.0.7.3bvrr6lyon.js:3 info: System.Net.Http.HttpClient.AbpMvcClient.ClientHandler[101]
      Received HTTP response headers after 160.1ms - 200
dotnet.runtime.8.0.7.3bvrr6lyon.js:3 info: System.Net.Http.HttpClient.AbpMvcClient.LogicalHandler[101]
      End processing HTTP request after 188.2ms - 200
dotnet.runtime.8.0.7.3bvrr6lyon.js:3  warn: Volo.Abp.IdentityModel.IdentityModelAuthenticationService[0]
      Could not find IdentityClientConfiguration for AbpMvcClient. Either define a configuration for AbpMvcClient or set a default configuration.
dotnet.runtime.8.0.7.3bvrr6lyon.js:3 info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[2]
      Authorization failed. These requirements were not met:
      DenyAnonymousAuthorizationRequirement: Requires an authenticated user.

Application Insights Logs

This issue does not present when logging into the main (admin) site. If subdomain tenant mapping is disabled the application works correctly.

Module Configuration Redacted.Blazor ---> RedactedBlazorModule.cs

• ABP Framework version: v8.2.0
• UI Type: Blazor Server
• Database System: EF Core
• **Azure Web App with AzureSignalR We've successfully implemented subdomain tenant mapping. However, when using linked accounts the subdomain does not change when the tenant change happens. How can we get the subdomain url to reflect the change in tentant?

Here is our WebModule configuration.

        PreConfigure<OpenIddictBuilder>(builder =>
        {
            _ = builder.AddValidation(options =>
            {
                _ = options.AddAudiences("SafetyPlusWeb");
                _ = options.UseLocalServer();
                _ = options.UseAspNetCore();
            });
        });

        if (!hostingEnvironment.IsDevelopment())
        {
            PreConfigure<AbpOpenIddictAspNetCoreOptions>(options =>
            {
                options.AddDevelopmentEncryptionAndSigningCertificate = false;
            });

            PreConfigure<OpenIddictServerBuilder>(serverBuilder =>
            {
                // In production, it is recommended to use two RSA certificates, 
                // one for encryption, one for signing.
                _ = serverBuilder.AddEncryptionCertificate(
                        GetEncryptionCertificate(context.Services.GetConfiguration()));
                _ = serverBuilder.AddSigningCertificate(
                        GetSigningCertificate(context.Services.GetConfiguration()));
            });

            var domainFormat = GetDomainFormatForEnvironment(hostingEnvironment);
            PreConfigure<AbpOpenIddictWildcardDomainOptions>(options =>
            {
                options.EnableWildcardDomainSupport = true;
                _ = options.WildcardDomainsFormat.Add($"https://{domainFormat}");
                _ = options.WildcardDomainsFormat.Add($"https://{domainFormat}/signin-oidc");
                _ = options.WildcardDomainsFormat.Add($"https://{domainFormat}/signout-callback-oidc");
            });
        }
    }

    public override void ConfigureServices(ServiceConfigurationContext context)
    {
        var hostingEnvironment = context.Services.GetHostingEnvironment();
        var configuration = context.Services.GetConfiguration();

        var domainFormat = GetDomainFormatForEnvironment(hostingEnvironment);

        Configure<AbpTenantResolveOptions>(options =>
        {
            options.AddDomainTenantResolver(domainFormat);
        });

        if (!configuration.GetValue<bool>("App:DisablePII"))
        {
            Microsoft.IdentityModel.Logging.IdentityModelEventSource.ShowPII = true;
        }

        if (!configuration.GetValue<bool>("AuthServer:RequireHttpsMetadata"))
        {
            Configure<OpenIddictServerAspNetCoreOptions>(options =>
            {
                options.DisableTransportSecurityRequirement = true;
            });
        }

        if (!hostingEnvironment.IsDevelopment())
        {
            _ = context.Services.AddSignalR(options =>
            {
                options.AddFilter<AbpMultiTenantHubFilter>();
            }).AddAzureSignalR();
        }

        ConfigureOptions(context, configuration);
        ConfigureAuthentication(context);
        ConfigureUrls(configuration);
        ConfigureBundles();
        ConfigureImpersonation(context, configuration);
        ConfigureAutoMapper();
        ConfigureVirtualFileSystem(hostingEnvironment);
        ConfigureMultiTenancy();
        ConfigureSwaggerServices(context.Services);
        ConfigureExternalProviders(context, configuration);
        ConfigureAutoApiControllers();
        ConfigureBlazorise(context);
        ConfigureRouter(context);
        ConfigureMenu(context);
        ConfigureCookieConsent(context);
        ConfigureAuditingOptions(context);
        ConfigureTheme();

        Configure<SettingManagementComponentOptions>(options =>
        {
            options.Contributors.Add(new SafetyPlusWebSettingsComponentContributor());
        });

        if (!hostingEnvironment.IsDevelopment())
        {
            Configure<AbpTenantResolveOptions>(options =>
            {
                options.AddDomainTenantResolver(domainFormat);
            });
        }
    }
    ```

• ABP Framework version: v8.0.4
• UI Type: Blazor Server
• Database System: EF Core (SQL Server)

Is it possible to bypass the "My Account" page with the linked account module and instead return directly to the previously opened page?