hi
This is a bug,We fixed it in new version.
hi
I want to know how to reproduce the issue on my local computer.
Thanks
hi
You can update abp packages to 7.3.3
or
Configure<AbpLayoutHookOptions>(options =>
{
options.Add(LayoutHooks.Head.Last, typeof(SyncfusionStyleComponent), layout: "Application");
options.Add(LayoutHooks.Body.Last, typeof(SyncfusionScriptComponent), layout: "Application");
});
Thanks.
hi
Can you create a new template project?
The project you shared uses the DevExpress and database migrations are incorrect.
Thanks.
hi
You can get an access_token from the authserver website and carry this token to the API.
https://auth0.com/docs/get-started/authentication-and-authorization-flow/which-oauth-2-0-flow-should-i-use
hi
Which project are you adding the ELSA dashboard to?
Similar questions: https://support.abp.io/QA/Questions/5733#answer-3a0db883-c466-1f48-be6b-ec834293db61
hi
What's your abp version? Are you using the latest lepton package?
Can you share an online URL? Include a test user. Thanks
liming.ma@volosoft.com
hi
This is normal behavior. Refreshing the page will solve the problem. The web project cannot always check whether the tenant exists.
hi
Is there a GivenName claim?
https://github.com/abpframework/abp/blob/dev/modules/identityserver/src/Volo.Abp.IdentityServer.Domain/Volo/Abp/IdentityServer/AspNetIdentity/AbpUserClaimsFactory.cs#L91
You can add your custom AbpUserClaimsFactory as well.
builder.Services.AddTransient<IUserClaimsPrincipalFactory<IdentityUser>, MyAbpUserClaimsFactory<IdentityUser>>();