Activities of "mert.kir"

  • ABP Framework version: v5.3.0
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes
  • Exception message and stack trace:
  • Steps to reproduce the issue:"
  1. On the Administration -> Identity Management -> Users page, when the Tenant name is clicked to logout, the import button stays on the page

  2. When Import -> External User is selected on the same page, it gives an error as "Your request is not valid".

  3. When Import -> External User is selected on the same page, if there is no provider to choose from, it gives an error message as "No external login provider available". The result is a warning message, not an error.

Items 2 and 3 are experienced in different projects. Can you help me?

Hello, I added the following code to the HttpApiHostModule and IdentityServerModule files. It works when I debug the line of code. However, after setting the tenant information to null, "tenant not found!" redirects to the page.

Configure<AbpAspNetCoreMultiTenancyOptions>(options =>
{
    options.MultiTenancyMiddlewareErrorPageBuilder = async (context, exception) =>
    {
        // Try to delete the tenant's cookie if it does not exist or is inactive.
        var tenantResolveResult = context.RequestServices.GetRequiredService<ITenantResolveResultAccessor>().Result;
        if (tenantResolveResult != null &&
        tenantResolveResult.AppliedResolvers.Contains(CookieTenantResolveContributor.ContributorName))
        {
            var options = context.RequestServices
            .GetRequiredService<IOptions<AbpAspNetCoreMultiTenancyOptions>>().Value;
            AbpMultiTenancyCookieHelper.SetTenantCookie(context, null, options.TenantKey);
        }
        
        context.Response.StatusCode = (int)HttpStatusCode.InternalServerError;
        context.Response.ContentType = "text/html";
        
        var message = exception.Message;
        var details = exception is BusinessException businessException
        ? businessException.Details
        : string.Empty;
        
        await context.Response.WriteAsync($"<html lang=\"{CultureInfo.CurrentCulture.Name}\"><body>\r\n");
        await context.Response.WriteAsync($"<h 3>{message}</h3>{details}<br>\r\n");
        await context.Response.WriteAsync("</body></html>\r\n");
        
        // Note the 500 spaces are to work around an IE 'feature'
        await context.Response.WriteAsync(new string(' ', 500));
    };
});

It will be available in 6.0. but you can change it by yourself now.

We have overwritten the modified code in the module file. It changes tenant information on the cookie but redirects to "tenant not found" exception page. It should redirect to main login page without any errors.

hi

Please custom the MultiTenancyMiddlewareErrorPageBuilder of AbpAspNetCoreMultiTenancyOptions to delete the cookies.

https://github.com/abpframework/abp/pull/13157

Hello, will this development be in the next first version?

Purging cache after deletion a tenant was shipped in v5.2.1.

Hi, I am using abp version 5.2.2 and the error still persists. I am writing steps how to reproduce the error.

  • A tenant named Test is created by entering the host in a browser.
  • The application is entered with the created tenant.
  • Then the application is exited and the login screen is displayed.
  • Login as host from a different browser and delete the Test tenant just created.
  • When we refresh the page we just logged out of, "Tenant not found! There is no tenant with the tenant id or name: 1e46a5e6-4fd1-ee24-a5c5-3a04ac356348".
  • As a workaround, you need to clear the browser's cache. The real solution to this needs to be done.

Can it be fixed with the first update?

All permissions are active when the DbMigrator project is running

  • ABP Framework version: v5.2.2
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes
  • Steps to reproduce the issue:
  1. Login to the application with one tenant.
  2. Go to Administration => Identity Management => Roles page.
  3. Some of the permissions of the admin role are removed.
  4. Then the DbMigrator project is run.
  5. When the permissions are looked again after the project is run, it is seen that all permissions are active.

With the DbMigrator project running, the permissions should remain as they are instead of being active again. How can I solve this problem?

Solution has been merged and will be shipped in v5.2.1 very soon

thanks, is there this improvement in current version 5.2.1? I'm asking because I can't see it in the changelog

  • ABP Framework version: v4.4.3
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes
  • Exception message and stack trace:
  • Steps to reproduce the issue:"

Hello, I am getting the following error when I inject IGuidGenaretor parameter to the constructor method of the AutoMapperProfile file in the Application layer. how can i solve this problem

Hello,

If you can download the source code, you can implement your fix until you upgrade your packages.

In organization-units.component.ts, after deleting a unit, you need to check if it is the selected unit.

Change

// ... 
.subscribe((status: Confirmation.Status) => { 
        if (status === Confirmation.Status.confirm) { 
          this.service.delete(id).subscribe(() => this.get()); 

to

// ... 
.subscribe((status: Confirmation.Status) => { 
        if (status === Confirmation.Status.confirm) { 
          this.service 
            .delete(id) 
            .pipe( 
              tap(_ => { 
                if (id === this.selectedUnit?.id) { 
                  this.selectedUnit = null; 
                } 
              }), 
            ) 
            .subscribe(() => this.get()); 
        } 
      }); 
 

thanks for the reply

It would be better to write information for those who have this problem under abp 5.0 version. Because after the statement that we will solve the problem, there was no information.

Showing 41 to 50 of 52 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on December 26, 2024, 06:07