oqapi/webgui
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

adding ldap recursive filter labels and hoverhelp

Browse source
This commit is contained in:
Frank Dillon 2006-07-12 20:27:29 +00:00
parent 1440fec057
commit 3937180957
1 changed files with 17 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

18
lib/WebGUI/i18n/English/AuthLDAP.pm
View file

@ -1,7 +1,23 @@
package WebGUI::i18n::English::AuthLDAP;
our $I18N = {
'ldap link name blank' => {
'global recursive filter label' => {
message => q|LDAP Recursive Group Filter|,
lastUpdate => 0
},
'global recursive filter label description' => {
message => q|Enter a string by which to filter out anything in your recursive ldap group that might not be a group. This is a performance setting which can help speed up the group search in the case where your groups and group members are both part of the same attribute used for groups of groups within LDAP. For example, if both users and groups are stored in the "member" attribute and users always contain the string o= while groups contain the string cn=, you might add o= as the filter in order that the code to recurse through the groups skips over the users in the group and only searches the groups. This setting will be applied to each LDAP group with recursive group settings. Optionally, you may choose to apply this setting to individual groups. The individual group setting will override the global setting|,
lastUpdate => 0
},
'LDAPLink_ldapRecursiveFilter' => {
message => q|LDAP Recursive Group Filter|,
lastUpdate => 0
},
'LDAPLink_ldapRecursiveFilterDescription' => {
message => q|Enter a string by which to filter out anything in your recursive ldap group that might not be a group. This is a performance setting which can help speed up the group search in the case where your groups and group members are both part of the same attribute used for groups of groups within LDAP. For example, if both users and groups are stored in the "member" attribute and users always contain the string o= while groups contain the string cn=, you might add o= as the filter in order that the code to recurse through the groups skips over the users in the group and only searches the groups. This setting will be applied to only this group. and will override any global filter you may have set for the ldap connection chosen.|,
lastUpdate => 0
},
'ldap link name blank' => {
message => q|The LDAP Link Name field cannot be blank.|,
lastUpdated => 0,
context => q|error message|