Hi,
You can check the document: https://identityserver4.readthedocs.io/en/latest/reference/options.html
Hi,
Seems there are no localized texts.
ABP will repeatedly try to get localized text. If it does not find localized text, it will affect performance.
https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.Localization/Volo/Abp/Localization/AbpDictionaryBasedStringLocalizer.cs#L127-L165
There are two solutions:
1 Add localized text to all permission groups and permission definitions
2 Using FixedLocalizableString
.
context.AddGroup("Group", new FixedLocalizableString("Group"));
group.AddPermission("Permission", new FixedLocalizableString("Permission"));
Hi,
1
You can ignore it if it's work.
2
Can you try this?
Configure<AbpBundlingOptions>(options =>
{
options.ScriptBundles.Configure(
LeptonXThemeBundles.Scripts.Global,
bundle =>
{
bundle.AddFiles("/myleptonx.js");
}
);
});
Hi,
I could not reproduce the problem.
Could you share a simple test project? My email is shiwei.liang@volosoft.com I will check it
: )
Hi,
First, use the module entity extension system to add a new property to the organization
. (I think you have completed this step.)
https://docs.abp.io/en/abp/latest/Module-Entity-Extensions#quick-example
Then, use the ef core entity extension system to make the property as a regular property in the entity
To overcome the difficulties described above, ABP Framework entity extension system for the Entity Framework Core that allows you to use the same extra properties API defined above, but store a desired property as a separate field in the database table.
https://docs.abp.io/en/abp/latest/Customizing-Application-Modules-Extending-Entities#entity-extensions-ef-core
Then you need to add and apply migration files: dotnet ef migrations add add_fullname_to_ou
, dotnet ef database update
Now, the FullName
is a shadow property, and you can access it in this way.
var query = await _organizationUnitRepository.GetQueryableAsync();
query.WhereIf(input.FullName.IsNotNullOrWhiteSpace(), e => EF.Property<string>(e, "FullName") == input.FullName);
Hi,
I have checked.
Did you try this and redeploy the application?
IdentityModelEventSource.ShowPII = true;
BTW It happens because the issuer is automatically set by the request. Set issuer to fix this problem In AuthServerModule.cs or HttpApiHostModule.cs as follows:
Configure<IdentityServerOptions>(options =>
{
options.IssuerUri = configuration["App:SelfUrl"];
});
Hi,
I guess the problem is related to localization.
Did you set the correct localized text for the permission definition?
I will check it
This is the problem of the IIS server.
You can check: https://stackoverflow.com/questions/4413455/why-does-http-delete-verb-return-405-error-method-not-allowed-for-my-restful-w