Last edited 10 months ago
by Redaktion

Reference:LDAPSyncAll: Difference between revisions

Redaktion (talk | contribs)
No edit summary
Tag: 2017 source edit
Redaktion (talk | contribs)
No edit summary
Line 8: Line 8:
|category=Infrastructure
|category=Infrastructure
|docu=https://www.mediawiki.org/wiki/Extension:LDAPSyncAll
|docu=https://www.mediawiki.org/wiki/Extension:LDAPSyncAll
|features=
|features=This extension provides a mechanism which synchronizes users in the database and users in Active Directory:
This extension provides a mechanism which synchronizes users in the database and users in Active Directory:


*If  a user is not in the database, but is in LDAP => the user will be added to the database
*If  a user is not in the database, but is in LDAP => the user will be added to the database


*If a user is in the database, but is not in LDAP => the user will be disabled in the database
*If a user is in the database, but is not in LDAP => the user will be disabled in the database
 
}}
{{wcagCheck
|wcagStatus=2-testing complete
|wcagTestdate=2022-08-05
|extensionType=backend
}}
}}

Revision as of 13:46, 5 August 2022

Extension: LDAPSyncAll

all extensions


Overview
Description: Mechanism which synchronizes users in the database and users in Active Directory. (v3.2 and up)
State: stable Dependency: MediaWiki
Developer: Robert Vogel License: -
Type: MediaWiki Category: Infrastructure
Edition: BlueSpice pro (deactivated), BlueSpice Farm (deactivated)"BlueSpice Farm (deactivated)" is not in the list (BlueSpice free, BlueSpice free (deactivated), BlueSpice pro, BlueSpice pro (deactivated), BlueSpice farm, BlueSpice farm (deactivated), BlueSpice cloud, BlueSpice cloud (deactivated)) of allowed values for the "BSExtensionInfoEdition" property. Version: 4.1+
For more info, visit Mediawiki.

Features

This extension provides a mechanism which synchronizes users in the database and users in Active Directory:

  • If a user is not in the database, but is in LDAP => the user will be added to the database
  • If a user is in the database, but is not in LDAP => the user will be disabled in the database

Accessibility

Test status: 2-testing complete
Last test date: 2022-08-05


Extension type: backend



To submit feedback about this documentation, visit our community forum.