Activities of "Spospisil"

Hi,

That's great but you still did not address how I can base 'all ABP 'admin' pages to be based on one layout and my application's pages to be based on another layout".

  • ABP Framework version: v7.3.3
  • UI Type: Blazor WASM
  • Database System: EF Core (PostgreSQL)
  • Tiered (for MVC) or Auth Server Separated (for Angular): yes

I have the need to have different layouts for my application depending on if you are in the 'admin' pages (users, saas tenants, editions, etc) vs the main application's pages. As shown below are the main applications page as well as the desired layout for my 'admin' pages, which in this case I'm showing the ABP user maintenance page. How can I accomplish this? I want all ABP 'admin' pages to be based on one layout and my application's pages to be based on another layout.

Thanks

Application Page Layout

<br> 'Admin' Page Layout

<br> <br>

Hi,

And defining the permission in this way will prevent it from showing as an option in the permission management UI?

Hi,

For example it would be helpful to have a 'IsVisibleToClients' property on the PermissionDefinition object (such as the case with Features) that allows the creation/use of a permission without showing it in the Permission Management UI.

  • ABP Framework version: v7.3.3
  • UI Type: Blazor WASM
  • Database System: EF Core (PostgreSQL)
  • Tiered (for MVC) or Auth Server Separated (for Angular): yes

Is it possible to create a tenant permission that is not visible in the permission management ui? I want to create a permission for a specific tenant facing page, but don't want the tenant to ever be able to see/change the value of that permission.

Thanks.

Answer

Thank you. That resolved the issue.

Answer

Hi,

Truly, it would be a lot quicker if you could produce a working sample of vs me trying to scale back my enterprise level application and all it's source code.

Could you please provide a sample based on blazor WASM tiered, etc?

Thanks.

Answer

Hi,

Is this the only thing I need to do to the code in order to get this to work? I keep getting the following message.

"Unhandled exception rendering component: The AuthorizationPolicy named: 'TenantPolicy' was not found."

private static void ConfigureAuthorization(ServiceConfigurationContext context)
{
    context.Services.AddAuthorization(options =>
    {
        options.AddPolicy("TenantPolicy", policy =>
        {
            policy.RequireAuthenticatedUser().RequireAssertion(handlerContext =>
            {
                var tenantId = handlerContext.User.FindTenantId();
                Console.WriteLine($"****** TenantId: {tenantId} ******");
                return false; // false to skip
            });

        });
    });
}
Question
  • ABP Framework version: v7.3.2
  • UI Type: Blazor WASM
  • Database System: EF Core/PostgreSQL
  • Tiered (for MVC) or Auth Server Separated (for Angular): yes

I want to be able to add a line of code (similar to below) to the top of every page that would only be available to a tenant without having to add a abp 'permission' or 'feature' definition but rather would pass the authorize test based on whether the current user's tenent id is null or not.

How can this be done in ABP?

@attribute [Authorize(TenantUser)]

  • ABP Framework version: v7.2.2
  • UI Type: Blazor WASM
  • Database System: EF Core (PostgreSQL)
  • Tiered (for MVC) or Auth Server Separated (for Angular): yes

Is there anyway to create Domain Entity classes from an existing database in ABP suite in bulk vs selecting them one at a time from ABP Suite? I have over 1000 tables in my DB I need to generate domain entities for.

Thanks.

Showing 121 to 130 of 375 entries
Learn More, Pay Less
33% OFF
All Trainings!
Get Your Deal
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.0.0-preview. Updated on September 12, 2025, 10:20