You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The data in the config should be respected. As it stands, even though it is an ISiteSettings value stored in the database, it is not registered as an Options (should it be?) and the IShellConfiguration is never consulted, so users cannot control these values from the config at all. Merely assigning values to the config values does NOT, e.g. override the display name of the existing AzureADSettings you've assigned via the admin GUI.
Because the values are forcibly being set via config, the UI should preset the values in the DisplayDriver and modify the View to disable editing of the fields, providing a hint that the values are being overridden by a config value (that way, people understand the reason it is blocking interaction).
Same is likely true for Microsoft Authentication since I haven't seen any mention of config in the module's source code at all. Possibly other External login providers, but I haven't checked those.
Screenshots
--
The text was updated successfully, but these errors were encountered:
Configure the AzureADSettings with IConfigureOptions
How to present all the ISiteSettings when they are also configured via IShellConfiguration - bearing in mind only some of the values may be set this way, some may still be set by the site settings.
For 1, I think it would be fine too refactor that to use IConfigureOptions as is done for many, but not all (there are many that it hasn't been done for) settings. Plenty of examples in the source code for this.
If you wanted to do a pr for this that would be great.
For 2 see #6036 for some discussion about it, again if someone wanted to work towards a solution, that would be great.
Describe the bug
Problems with configuring AzureADSettings in answer to #8432.
To Reproduce
Steps to reproduce the behavior:
Microsoft Azure Active Directory Authentication
feature.appsettings.json
to look like this:Expected behavior
The data in the config should be respected. As it stands, even though it is an ISiteSettings value stored in the database, it is not registered as an Options (should it be?) and the IShellConfiguration is never consulted, so users cannot control these values from the config at all. Merely assigning values to the config values does NOT, e.g. override the display name of the existing AzureADSettings you've assigned via the admin GUI.
Because the values are forcibly being set via config, the UI should preset the values in the DisplayDriver and modify the View to disable editing of the fields, providing a hint that the values are being overridden by a config value (that way, people understand the reason it is blocking interaction).
Same is likely true for Microsoft Authentication since I haven't seen any mention of config in the module's source code at all. Possibly other External login providers, but I haven't checked those.
Screenshots
--
The text was updated successfully, but these errors were encountered: