<pclass="ldapIndent"><labelfor="ldap_expert_uuid_user_attr"><?phpp($l->t('UUID Attribute for Users:'));?></label><inputtype="text"id="ldap_expert_uuid_user_attr"name="ldap_expert_uuid_user_attr"data-default="<?phpp($_['ldap_expert_uuid_user_attr_default']);?>"/></p>
<pclass="ldapIndent"><labelfor="ldap_expert_uuid_group_attr"><?phpp($l->t('UUID Attribute for Groups:'));?></label><inputtype="text"id="ldap_expert_uuid_group_attr"name="ldap_expert_uuid_group_attr"data-default="<?phpp($_['ldap_expert_uuid_group_attr_default']);?>"/></p>
<p><strong><?phpp($l->t('Username-LDAP User Mapping'));?></strong></p>
<pclass="ldapIndent"><?phpp($l->t('Usernames are used to store and assign (meta) data. In order to precisely identify and recognize users, each LDAP user will have a 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.'));?></p>
<pclass="ldapIndent"><?phpp($l->t('Usernames are used to store and assign (meta) data. 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.'));?></p>
<pclass="ldapIndent"><buttontype="button"id="ldap_action_clear_user_mappings"name="ldap_action_clear_user_mappings"><?phpp($l->t('Clear Username-LDAP User Mapping'));?></button><br/><buttontype="button"id="ldap_action_clear_group_mappings"name="ldap_action_clear_group_mappings"><?phpp($l->t('Clear Groupname-LDAP Group Mapping'));?></button></p>
t('core','Your web server is not yet properly setup to allow files synchronization because the WebDAV interface seems to be broken.')
t('core','Your web server is not yet set up properly to allow file synchronization because the WebDAV interface seems to be broken.')
);
}
deferred.resolve(messages);
...
...
@@ -51,12 +51,12 @@
if (xhr.status===200&&data){
if (!data.serverHasInternetConnection){
messages.push(
t('core','This server has no working internet connection. This means that some of the features like mounting of external storage, notifications about updates or installation of 3rdparty apps don´t work. Accessing files from remote and sending of notification emails might also not work. We suggest to enable internet connection for this server if you want to have all features.')
t('core','This server has no working Internet connection. This means that some of the features like mounting external storage, notifications about updates or installation of third-party apps will not work. Accessing files remotely and sending of notification emails might not work, either. We suggest to enable Internet connection for this server if you want to have all features.')
);
}
if(!data.dataDirectoryProtected){
messages.push(
t('core','Your data directory and your files are probably accessible from the internet. The .htaccess file is not working. We strongly suggest that you configure your webserver in a way that the data directory is no longer accessible or you move the data directory outside the webserver document root.')
t('core','Your data directory and your files are probably accessible from the Internet. The .htaccess file is not working. We strongly suggest that you configure your webserver in a way that the data directory is no longer accessible or you move the data directory outside the webserver document root.')