View | Details | Raw Unified | Return to bug 33699
Collapse All | Expand All

(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/admin/identity_provider_domains.tt (-19 / +8 lines)
Lines 91-107 Link Here
91
                        <input type="text" name="domain" id="domain" size="60" />
91
                        <input type="text" name="domain" id="domain" size="60" />
92
                        <div class="hint">Email domain to match this rule. <button class="more btn btn-ligth" data-target="domain"><i class="fa fa-caret-down"></i> More</button></div>
92
                        <div class="hint">Email domain to match this rule. <button class="more btn btn-ligth" data-target="domain"><i class="fa fa-caret-down"></i> More</button></div>
93
                        <div class="hint more-domain" style="display: none">
93
                        <div class="hint more-domain" style="display: none">
94
                            <div>If this field is empty, or '*' any email domain will match this rule.</div>
94
                            <p>If this field is empty, or '*' any email domain will match this rule.</p>
95
                            <div>You may enter a wildcard at the beginning of the domain. For example, the domain '*library.com' will match 'students.library.com' but will also match 'otherlibrary.com'</div>
95
                            <p>You may enter a wildcard at the beginning of the domain. For example, the domain '*library.com' will match 'students.library.com' but will also match 'otherlibrary.com'</p>
96
                            <div>Exact matches have presedence over wildcard ones, so 'library.com' domain will take presedence over '*library.com' when the email is 'somebody@library.com'</div>
96
                            <p>Exact matches have precedence over wildcard ones, so 'library.com' domain will take precedence over '*library.com' when the email is 'somebody@library.com'</p>
97
                            <div>The same way, the longest match will take presedence over the shorter one, so '*teacher.university.com' will take presedence over '*.university.com' if the email is 'user@math.teacher.university.com'</div>
97
                            <p>The same way, the longest match will take precedence over the shorter one, so '*teacher.university.com' will take precedence over '*.university.com' if the email is 'user@math.teacher.university.com'</p>
98
                        </div>
98
                        </div>
99
                    </li>
99
                    </li>
100
                </ol>
101
            </fieldset>
102
103
            <fieldset class="rows">
104
                <ol>
105
                    <li>
100
                    <li>
106
                        <label for="update_on_auth">Update on login: </label>
101
                        <label for="update_on_auth">Update on login: </label>
107
                        <select name="update_on_auth" id="update_on_auth">
102
                        <select name="update_on_auth" id="update_on_auth">
Lines 178-194 Link Here
178
                        <input type="text" name="domain" id="domain" size="60" value="[%- identity_provider_domain.domain | html -%]"/>
173
                        <input type="text" name="domain" id="domain" size="60" value="[%- identity_provider_domain.domain | html -%]"/>
179
                        <div class="hint">Email domain to match this rule. <button class="more btn btn-ligth" data-target="domain"><i class="fa fa-caret-down"></i> More</button></div>
174
                        <div class="hint">Email domain to match this rule. <button class="more btn btn-ligth" data-target="domain"><i class="fa fa-caret-down"></i> More</button></div>
180
                        <div class="hint more-domain" style="display: none">
175
                        <div class="hint more-domain" style="display: none">
181
                            <div>If this field is empty, or '*' any email domain will match this rule.</div>
176
                            <p>If this field is empty, or '*' any email domain will match this rule.</p>
182
                            <div>You may enter a wildcard at the beginning of the domain. For example, the domain '*library.com' will match 'students.library.com' but will also match 'otherlibrary.com'</div>
177
                            <p>You may enter a wildcard at the beginning of the domain. For example, the domain '*library.com' will match 'students.library.com' but will also match 'otherlibrary.com'</p>
183
                            <div>Exact matches have presedence over asterix ones, so if the 'library.com' domain will take presedence over '*library.com' when the email is 'somebody@library.com'</div>
178
                            <p>Exact matches have precedence over asterix ones, so 'library.com' will take precedence over '*library.com' when the email is 'somebody@library.com'</p>
184
                            <div>The same way, the longest match will take presedence over the shorter one, so '*teacher.university.com' will take presedence over '*.university.com' if the email is 'user@math.teacher.university.com'</div>
179
                            <p>The same way, the longest match will take precedence over the shorter one, so '*teacher.university.com' will take precedence over '*.university.com' if the email is 'user@math.teacher.university.com'</p>
185
                        </div>
180
                        </div>
186
                    </li>
181
                    </li>
187
                </ol>
188
            </fieldset>
189
190
            <fieldset class="rows">
191
                <ol>
192
                    <li>
182
                    <li>
193
                        <label for="update_on_auth">Update on login: </label>
183
                        <label for="update_on_auth">Update on login: </label>
194
                        <select name="update_on_auth" id="update_on_auth">
184
                        <select name="update_on_auth" id="update_on_auth">
195
- 

Return to bug 33699