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

29 lines
1.3 KiB
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}}
demo-orgs: Disable admin of authentication methods until email set. Because demo organization owners do not initially have an email set, some of the personal and organization settings in the web-app UI should be disabled/hidden until the owner configures an email address for their account. Disables configuring organization authentication methods in the organization settings overlay until the user has configured an email address. Adds a tip at the top of the authentication methods tab to indicate why the authentication method checkboxes are disabled.
2023-01-20 18:29:34 +01:00
{{#unless user_has_email_set}}
demo-orgs: Add section on configuring email address to help article. Adds a section to the demo organizations help center article about configuring an email and password for demo organization owners. For demo organization warning banners about needing to configure an email, add a link to the new section in the help article. Also, adds a related articles section to the help center article, and updates the current draft text for changes in how the demo organization feature is being implemented.
2023-09-01 12:32:53 +02:00
<div class="tip">
{{#tr}}
You must <z-link>configure your email</z-link> to access this feature.
{{#*inline "z-link"}}<a href="/help/demo-organizations#configure-email-for-demo-organization-owner" target="_blank" rel="noopener noreferrer">{{> @partial-block }}</a>{{/inline}}
{{/tr}}
</div>
demo-orgs: Disable admin of authentication methods until email set. Because demo organization owners do not initially have an email set, some of the personal and organization settings in the web-app UI should be disabled/hidden until the owner configures an email address for their account. Disables configuring organization authentication methods in the organization settings overlay until the user has configured an email address. Adds a tip at the top of the authentication methods tab to indicate why the authentication method checkboxes are disabled.
2023-01-20 18:29:34 +01:00
{{/unless}}
settings: Remove form-horizontal class in org settings pages. This commit removes form-horizontal class from form elements in custom-emoji, linkifiers, playgrounds, default-streams, default-user-settings, auth-methods and user privacy settings templates. We can safely remove this class because vertical-align property for input elements is set by other bootstrap CSS and margin property for text inputs is set in app_components.css and for checkbox inputs it is set by bootstrap itself. The display property for inputs other than checkbox and select elements is set to inline-block by other bootstrap CSS. For checkbox-type inputs browser sets display property to inline-block but it is eventually computed to "block" as the float property is set to left.
2023-01-10 11:13:05 +01:00
<form class="admin-realm-form org-authentications-form">
settings: Remove unused admin-table-wrapper class. This class is not used anywhere, so there is no need for this.
2024-07-08 16:15:33 +02:00
<div id="org-auth_settings" class="settings-subsection-parent">
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 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: Refactor code to handle realm authentication methods. This commit refactors code to handle realm authentication methods in a better way. We remove the get_complete_data_for_subsection function and instead let populate_data_for_request handle the request data for authentication methods. We also remove the "prop-element" class from each authentication setting checkbox and instead add it to the container div as a the list of those checkboxes represent a single field, i.e. the realm_authentication_methods field received from the server and the authentication_methods field sent to 'PATCH /realm' endpoint.
2024-05-28 15:52:21 +02:00
<div id="id_realm_authentication_methods" class="prop-element" data-setting-widget-type="auth-methods">
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
{{! 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>