I noticed even in ABP 8 application (Micro Service), Abp Audit Log has a lot of exception:
/api/account/my-profile [ { "code": "Volo.Authorization:010001", "message": "Authorization failed! Given policy has not granted.", "details": null, "data": {}, "validationErrors": null } ]
1 Answer(s)
-
0
The "Authorization failed! Given policy has not granted." error for /api/account/my-profile in ABP 8 microservice applications is typically caused by missing or misconfigured permissions or claims for the authenticated user.
In ABP microservice solutions, especially after upgrading to v8.0, this issue can also be related to the configuration of dynamic claims or claim type updates in IdentityServer.
If you are using IdentityServer, ensure that you have the following configuration in your IdentityServer host module to prevent claim type mismatches:
public override void PreConfigureServices(ServiceConfigurationContext context) { context.Services.PreConfigure<AbpIdentityServerBuilderOptions>(options => { options.UpdateAbpClaimTypes = false; }); }
Also, if you have enabled dynamic claims, try disabling it by removing or setting the following configuration to false:
context.Services.Configure<AbpClaimsPrincipalFactoryOptions>(options => { options.IsDynamicClaimsEnabled = false; });
Make sure the user has the required permissions for the endpoint. You can check and assign the necessary permissions in the Identity Management UI or via code.
If deploying behind IIS or a reverse proxy, ensure authentication headers are forwarded correctly.
For more details and troubleshooting steps, see the following validated resources:
Sources:
- https://abp.io/support/questions/6432
- https://abp.io/support/questions/611
- https://abp.io/support/questions/2937
- https://docs.abp.io/en/abp/latest/Dynamic-Claims
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.