Hi,
The StaticPermissionSaver
will remove old permissions.
https://github.com/abpframework/abp/blob/rel-8.2/modules/permission-management/src/Volo.Abp.PermissionManagement.Domain/Volo/Abp/PermissionManagement/StaticPermissionSaver.cs#L186
you can use PermissionOptions
to configure them.
Configure<AbpPermissionOptions>(options =>
{
options.DeletedPermissions = ...;
options.DeletedPermissionGroups = ...;
});
Hi,
But from angular side, when sending application-configuration request (which includes in its response auth -> grantedPolicies to tell angular app current users' permissions, I don't see my permission granted!
You may need to custom the AbpApplicationConfigurationAppService
service
https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.AspNetCore.Mvc/Volo/Abp/AspNetCore/Mvc/ApplicationConfigurations/AbpApplicationConfigurationAppService.cs
HI.
Sorry for the confusion, I mean your app account.
https://stackoverflow.com/questions/49389306/stop-sharing-cookies-between-applications-under-same-site-id-in-iis
// your SSO project
context.Services.ConfigureApplicationCookie(options =>
{
options.Cookie.Path = "/auth"; // or /sso anything you wants
});
Configure<AbpAntiForgeryOptions>(options =>
{
options.TokenCookie.Path = "/auth";
});
Hi,
The problem is ng sends the wrong cookies to the API backend.
These cookies come from the SSO server.
you can set different cookie path for your SSO server