Yes, you are right.
Sorry, I had changed the value in the wrong place on the web, in the Standard Editions Features. Now, I have changed the value in "Manager Host Features" and that's correct.
I am glad it is working.
Please, cloud you tell me how I can block the login, using the feature loginEnabled and if role is not admin?
Normally, you should to open a separate ticket for this, but if I need to give brief information, you can override the OnPost method of the Login page model and add the logic you want before calling base.OnPost.
Here are the related contents:
Closing the issue. Feel free to create a new issue if you have further questions.
Reproduction is 1/2 way there ;-). Note the screencaps of the "variable" missing during the forced debug. I think there is a hash/array that went out of bounds and everything breaks. Probably i went past original-designed upper bounds of "normal app use" and moved us in to edge/extreme. "128 fields, yeah! thats enough!". Nope.
This is a manufacturing floor Line-of-business app. The dashboard will-have literally 300 fields once pivoted.
Yes, I have been working as an ABP maintainer for 5 years, but this is the first time I have come across such a case. But we like edge cases :)
We will examine your problem and try to return as soon as possible. Thank you for your patience.
Hello,
Can you update the cookie addition part of the ConfigureAuthentication method of the MyAppBlazorModule class as follows and try again?
.AddCookie("Cookies", options =>
{
options.ExpireTimeSpan = TimeSpan.FromDays(365);
options.SlidingExpiration = true;
options.Cookie.HttpOnly = true;
options.Cookie.SecurePolicy = CookieSecurePolicy.Always;
options.Cookie.SameSite = SameSiteMode.None;
options.Cookie.IsEssential = true; // Ensure cookies are not cleared by tracking prevention
options.IntrospectAccessToken();
})
Enis is off today, so we'll answer on Monday. Thank you for your patience.
Sorry for the late reply, but we missed this question because the friend dealing with the subject was on vacation. However, next Monday, the friend who is interested in the subject will return to you. Thank you for your patience.
Enis is off today, so we'll answer on Monday. Thank you for your patience.
It shouldn't, but you can let us know if there is a problem. We are waiting to hear from you for now.
Hi,
Yes, I was able to reproduce the problem, I have opened an internal issue to investigate it in more detail. It seems to take a long time to determine the problem, but we will inform you as soon as we determine it. Thank you for your patience.
Thanks, I examined the DBContext you sent, but I couldn't come to a conclusion. Do you have a chance to send your complete project so we can solve it faster? Because I cannot reproduce this problem when I created a project from scratch.
Hi,
I missed what you wrote because someone else replied. If you want, we can schedule it for Monday?
