Thanks. Adding it to the host application fixed my problem.
[AI-Bot] said: This is a known behavior in ABP Framework. When you set "Abp.Account.IsSelfRegistrationEnabled" in the AuthServer's appsettings.json, it only sets the default value for the setting. The UI on the settings page (host/tenant → Account tab) displays the value from the AbpSettings table, not the default from appsettings.json. If there is no record in the AbpSettings table, the UI will show the default (which is "true" unless overridden in the database), even if the actual behavior is "false" due to your appsettings.json.
Once you toggle and save the setting in the UI, a record is created in the AbpSettings table, and the UI will then reflect the correct value.
Workaround / Solution:
- To ensure the UI matches the actual behavior, you should create a record in the AbpSettings table for "Abp.Account.IsSelfRegistrationEnabled" with the value you want (e.g., "false") for the relevant provider (host/tenant).
- Alternatively, toggle and save the setting once in the UI to create the record.
Why this happens:
ABP's setting system uses the following precedence:
- Value in the AbpSettings table (per provider/tenant)
- Default value from code or appsettings.json (if no record in DB)
The UI only reads from the database, not from appsettings.json, unless a record is created.
References:
- ABP Support: Email settings not visible for tenant
- ABP Support: Email settings permission for tenant
This is the expected design in ABP Framework. If you want the UI to always reflect the appsettings.json value, you would need to customize the settings management UI to also read from configuration, which is not the default behavior.
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.
However, from a user perspective, it feels inconsistent that the backend behavior (self-registration disabled via appsettings.json) does not match what the UI displays on the settings page. This can easily cause confusion for administrators who rely on the UI to verify the system’s configuration.
