diff options
| author | Nextcloud bot <bot@nextcloud.com> | 2021-02-02 02:19:50 +0000 |
|---|---|---|
| committer | Nextcloud bot <bot@nextcloud.com> | 2021-02-02 02:19:50 +0000 |
| commit | e18c608cb470081e9ad1342b0abb0a7acb2fe458 (patch) | |
| tree | c8f79767bbc30c3b9cb15968454ca4161fc5fe58 /apps/user_ldap/l10n/en_GB.js | |
| parent | 86678ba5df7b74fab9ac739ca17109cd717f8062 (diff) | |
| download | nextcloud-server-e18c608cb470081e9ad1342b0abb0a7acb2fe458.tar.gz nextcloud-server-e18c608cb470081e9ad1342b0abb0a7acb2fe458.zip | |
[tx-robot] updated from transifex
Diffstat (limited to 'apps/user_ldap/l10n/en_GB.js')
| -rw-r--r-- | apps/user_ldap/l10n/en_GB.js | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/apps/user_ldap/l10n/en_GB.js b/apps/user_ldap/l10n/en_GB.js index f9c5bccf5b6..9373cb7eead 100644 --- a/apps/user_ldap/l10n/en_GB.js +++ b/apps/user_ldap/l10n/en_GB.js @@ -185,7 +185,6 @@ OC.L10N.register( "Username-LDAP User Mapping" : "Username-LDAP User Mapping", "Usernames are used to store and assign metadata. In order to precisely identify and recognize users, each LDAP user will have an internal username. This requires a mapping from username to LDAP user. The created username is mapped to the UUID of the LDAP user. Additionally the DN is cached as well to reduce LDAP interaction, but it is not used for identification. If the DN changes, the changes will be found. The internal username is used all over. Clearing the mappings will have leftovers everywhere. Clearing the mappings is not configuration sensitive, it affects all LDAP configurations! Never clear the mappings in a production environment, only in a testing or experimental stage." : "Usernames are used to store and assign metadata. In order to precisely identify and recognise users, each LDAP user will have an internal username. This requires a mapping from username to LDAP user. The created username is mapped to the UUID of the LDAP user. Additionally the DN is cached as well to reduce LDAP interaction, but it is not used for identification. If the DN changes, the changes will be found. The internal username is used all over. Clearing the mappings will have leftovers everywhere. Clearing the mappings is not configuration sensitive, it affects all LDAP configurations! Never clear the mappings in a production environment, only in a testing or experimental stage.", "Clear Username-LDAP User Mapping" : "Clear Username-LDAP User Mapping", - "Clear Groupname-LDAP Group Mapping" : "Clear Groupname-LDAP Group Mapping", - "Leave empty for user name (default). Otherwise, specify an LDAP/AD attribute." : "Leave empty for user name (default). Otherwise, specify an LDAP/AD attribute." + "Clear Groupname-LDAP Group Mapping" : "Clear Groupname-LDAP Group Mapping" }, "nplurals=2; plural=(n != 1);"); |