Skip to content

Technical Plugin LoginLDAP

Daniel Neto edited this page Oct 29, 2026 · 1 revision

Technical: LoginLDAP plugin

Authenticates against LDAP/Active Directory.

Audience: developers, advanced administrators and AI-assisted diagnosis. Plugin catalog.

Source baseline

  • Review date: 2026-10-29. Method: static source analysis; runtime/provider behavior was not exercised.
  • Code ownership: independently versioned plugin repository.
  • Reported version: 3.9.
  • Source revision: bd4b0bf40dc5cc8f7187c8cf1ba9944f53225d8d.
  • Entry class file: LoginLDAP.php.

Confirm the installed plugin version independently of the Streamer version. Configuration defaults below are not a dump of this installation's saved settings.

Dependencies

No literal dependency declaration was extracted. This does not prove the plugin is standalone.

Literal runtime plugin references: LoginWordPress. These calls do not mean every referenced plugin is mandatory.

Hook integration

Override Implementation
getTags() LoginLDAP.php:7
getLogin() LoginLDAP.php:55

Configuration assignments

These are direct assignments inside getEmptyDataObject(), not evaluated effective defaults. Stored plugins.object_data, globals, structured values and conditional branches may alter runtime behavior. Private/default credential values are omitted.

Field Literal default or expression type Literal source label/help Evidence
server "" — source
port "389" — source
rdn Computed/structured; inspect source — source
filter Computed/structured; inspect source — source
LDAP_OPT_PROTOCOL_VERSION 3 — source
defaultProfilePhoto Computed/structured; inspect source — source
savePassword Private setting; value omitted — source
disableNativeSignUp true — source
disableRecoverDatabasePassword Private setting; value omitted — source
ifLdapLoginFailTryDatabase false — source
hideLdapBottomInfo false — source
autoAddNewUsersOnUserGroup Computed/structured; inspect source Auto add new users on UserGroup: When a new user is created with the LDAP, this user will be auto added on the selected user group source

Files and request surface

This inventory distinguishes implementation files from an API specification. Includes, templates, callbacks and CLI workers are not interchangeable HTTP endpoints. Request-field names below are direct source references, not a complete schema or permission declaration.

File Source role Direct request fields observed
LoginLDAP.php plugin entry class —
view/login.json.php JSON entry point; inspect caller and guard do_not_login, pass, user
view/loginForm.php PHP page/include/worker; inspect caller —

Data and migrations

No CREATE TABLE names were extracted from available plugin SQL. The plugin can still use core tables, PHP-created schema or another component's data. Apply installation/update behavior through the owning plugin; this reference is not a script for running historical migrations manually.

Main-file named symbols

Visibility and implementation semantics must be checked in source. Nonempty string defaults are represented as . This is a symbol reference, not a stable public API promise.

Function or method Source
getTags() 7
getDescription() 14
getName() 20
getUUID() 24
getEmptyDataObject() 28
getLogin() 55
getPluginVersion() 60
auth($user, $pass) 64
tryDatabaseOrUserNotFound($user, $pass) 108
authSearch($user, $pass) 118
login($user, $pass) 177

Diagnostics and validation

  1. Check the installed/enabled version and the dependencies/settings above.
  2. Identify the actual failing page, request, callback or worker and correlate its timestamp with the AVideo log.
  3. Follow the linked method and caller. Check business-state changes and output artifacts as well as HTTP status.
  4. Reproduce the relevant workflow in a test environment. External provider, Encoder, live-server, storage, payment and authenticated flows require their real integrations.

Shared diagnostic workflow. This page is not a security audit or a claim of end-to-end validation.

Clone this wiki locally