I already set the lockout settings to a maximum of 6 access attempts, but it only works for non-tenant users.
Non tenant user :
For tenant users, the maximum access attempts are still detected as 5 :
How can I configure the lockout settings so that they apply to both tenant and non-tenant users?
4 Answer(s)
-
0
In ABP, lockout settings such as "Max failed access attempts" are managed via the Identity module and can be set per tenant. If tenant users are still using the default value (5) instead of your configured value (6), it is likely because the setting was only changed for the host, not for the tenant.
Each tenant has its own settings scope. Changing the lockout settings as the host only affects host users. To apply the new lockout value to tenant users, you must log in as the tenant admin, go to the Settings > Identity Management > Lockout settings page, and set the value for that tenant.
If you want to enforce the same lockout policy for all tenants, you can:
- Set the default value in your custom SettingDefinitionProvider.
- Use the "Set for all tenants" feature (if available in your ABP version).
- Programmatically update the setting for all tenants using the ISettingManager service.
Summary: Update the lockout settings for each tenant individually, or set the default value globally in code to ensure all tenants use the same configuration.
This approach aligns with common ABP conventions, but specific official documentation for this exact scenario is not available.
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.
-
0
hi
Can you check your
AbpSettingstable values in the database? make sure the tenant has no setting values.Thanks.
-
0
Okey solve. Thanks
-
0
Great
