hi
You can try
BundleManager
to remove the WatchChanges
Thanks.
hi
isGranted variable doesn't relfect the latest value when role is updated in this method before get to this line,
You can Changing the Current Principal
and then check the permission.
https://abp.io/docs/latest/framework/infrastructure/current-user#changing-the-current-principal
The permission check will use the values from CurrentUser
.
hi
Is there a AbpLicenseCode
in your appsettings.json
?
And see https://abp.io/support/questions/817/How-to-delete-current-license-login-session#answer-4cbc8f13-c7f3-84fa-7fc8-39fa2688df13
hi
I will ask our team.
hi
What is your license type?
Team or Business?
Thanks.
hi
We will fix this in 9.0
https://github.com/abpframework/abp/pull/21263
You can override the Volo.Abp.Identity:InvalidUserName
text and add the patch code below to your API website.
"Volo.Abp.Identity:InvalidUserName": "Username '{0}' is invalid, can only contain letters or digits."
public class Program
{
public async static Task<int> Main(string[] args)
{
var identityStrings = (typeof(AbpIdentityResultExtensions)
.GetField("IdentityStrings", BindingFlags.NonPublic | BindingFlags.Static | BindingFlags.Instance)
?.GetValue(null) ?? new Dictionary<string, string>()).As<Dictionary<string, string>>();
if (identityStrings.ContainsKey("InvalidUserName"))
{
identityStrings["InvalidUserName"] = "Username '{0}' is invalid.";
}
https://abp.io/community/articles/how-to-override-localization-strings-of-depending-modules-ba1oy03l
The Login
page will lose the Prevent Cross-Site Request Forgery (XSRF/CSRF)
feature.
https://learn.microsoft.com/en-us/aspnet/core/security/anti-request-forgery?view=aspnetcore-8.0