Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/static/templates/settings/auth_methods_settings_admin...

21 lines
924 B
Handlebars
Raw Normal View History

org settings: Add save/discard widget for realm authentication methods. Along with this, we refactored settings_org.populate_auth_methods to use HTML function after rendering all auth methods rows rather than appending each row individually, which actually is a good practice. Also in this commit, to compare `current_val` and `changed_val` in `check_property_changed` function of the property `realm_authentication_methods`, which are objects, and we found here https://stackoverflow.com/a/1144249 that there is no easy way to do so. So I followed this approach, ```js JSON.stringify(obj1) === JSON.stringify(obj2) ``` but before converting them to string we want the same order of keys, so we used `sort_object_by_key` to sort `current_val` by keys and `get_auth_method_table_data` always return `changed_val` having keys sorted. Since these refactor were closely related we kept them as a single commit here. Fixes: #11954.
2019-04-06 08:43:34 +02:00
<div id="organization-auth-settings" class="settings-section" data-name="auth-methods">
realm: Allow only owners to configure auth methods for a realm. This commit adds the restriction on configuring auth methods for admins. We now allow only owners to configure the auth methods for realm.
2020-06-11 16:24:15 +02:00
{{#unless is_owner}}
<div class='tip'>{{t "Only organization owners can edit these settings."}}</div>
{{/unless}}
settings_org: Split out separate forms for orgs settings/permissions/auth. Steve Howell also contributed to this PR.
2017-05-25 00:50:07 +02:00
<form class="form-horizontal admin-realm-form org-authentications-form">
org settings: Add save/discard widget for realm authentication methods. Along with this, we refactored settings_org.populate_auth_methods to use HTML function after rendering all auth methods rows rather than appending each row individually, which actually is a good practice. Also in this commit, to compare `current_val` and `changed_val` in `check_property_changed` function of the property `realm_authentication_methods`, which are objects, and we found here https://stackoverflow.com/a/1144249 that there is no easy way to do so. So I followed this approach, ```js JSON.stringify(obj1) === JSON.stringify(obj2) ``` but before converting them to string we want the same order of keys, so we used `sort_object_by_key` to sort `current_val` by keys and `get_auth_method_table_data` always return `changed_val` having keys sorted. Since these refactor were closely related we kept them as a single commit here. Fixes: #11954.
2019-04-06 08:43:34 +02:00
<div id="org-auth_settings" class="admin-table-wrapper org-subsection-parent">
<div class ="subsection-header">
<h3>{{t "Authentication methods" }}</h3>
templates: Use upstream Handlebars partials syntax. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-11 04:05:28 +02:00
{{> settings_save_discard_widget section_name="auth_settings" }}
org settings: Add save/discard widget for realm authentication methods. Along with this, we refactored settings_org.populate_auth_methods to use HTML function after rendering all auth methods rows rather than appending each row individually, which actually is a good practice. Also in this commit, to compare `current_val` and `changed_val` in `check_property_changed` function of the property `realm_authentication_methods`, which are objects, and we found here https://stackoverflow.com/a/1144249 that there is no easy way to do so. So I followed this approach, ```js JSON.stringify(obj1) === JSON.stringify(obj2) ``` but before converting them to string we want the same order of keys, so we used `sort_object_by_key` to sort `current_val` by keys and `get_auth_method_table_data` always return `changed_val` having keys sorted. Since these refactor were closely related we kept them as a single commit here. Fixes: #11954.
2019-04-06 08:43:34 +02:00
</div>
<div>
<p>{{t "Configure the authentication methods for your organization."}}</p>
settings_org: Use settings_checkbox in Authentication Methods UI. Per review feedback in #21002, replace HTML table with a series of settings_checkbox components for Authentication Methods UI. Fixes #21001.
2022-07-07 10:12:16 +02:00
<div id="id_realm_authentication_methods">
{{! Empty div is intentional, it will get populated by a dedicated template }}
</div>
org settings: Add save/discard widget for realm authentication methods. Along with this, we refactored settings_org.populate_auth_methods to use HTML function after rendering all auth methods rows rather than appending each row individually, which actually is a good practice. Also in this commit, to compare `current_val` and `changed_val` in `check_property_changed` function of the property `realm_authentication_methods`, which are objects, and we found here https://stackoverflow.com/a/1144249 that there is no easy way to do so. So I followed this approach, ```js JSON.stringify(obj1) === JSON.stringify(obj2) ``` but before converting them to string we want the same order of keys, so we used `sort_object_by_key` to sort `current_val` by keys and `get_auth_method_table_data` always return `changed_val` having keys sorted. Since these refactor were closely related we kept them as a single commit here. Fixes: #11954.
2019-04-06 08:43:34 +02:00
</div>
admin: Enable admins to toggle supported auth methods via UI. Add a table to the administration page that will allow realm admins to activate and deactivate the supported authentication methods for that realm.
2016-11-02 21:51:56 +01:00
</div>
Clean auth-methods-settings-admin.handlebars to use 4 space indents.
2017-04-26 04:40:23 +02:00
</form>
admin: Enable admins to toggle supported auth methods via UI. Add a table to the administration page that will allow realm admins to activate and deactivate the supported authentication methods for that realm.
2016-11-02 21:51:56 +01:00
</div>