Developer hooks

Use WordPress filters and actions to extend authentication, account data, and settings.

Simple LDAP Login keeps its legacy hook names and adds hooks for directory modules and account management. Put custom code in a site plugin. Test it with password login, SSO, tests, and scheduled jobs as applicable.

Shared filters

FilterPurpose
sll_get_settingFilter one setting value. Receives value and setting key.
sll_force_ldapLegacy recovery policy. Its inverted meaning is kept: false requires LDAP. It applies to legacy recovery mode.
sll_remove_default_authentication_hookControls local fallback policy. It no longer removes core or third-party authentication filters.
sll_ldap_authMay reject a successful bind. It cannot turn a failed bind into a verified identity.
sll_user_has_groupsFilters the group access result.
sll_ldap_attributesAdd directory attributes needed by a module. Attribute names are validated.
sll_ldap_entryAdd checked directory data after group access passes. Receives the entry array, connection, directory model, and login name.
sll_user_dataFilter new WordPress account data before creation.
sll_account_verifiedReject an identity before account update actions. Receives the WordPress user and entry.
sll_settings_defaultsAdd module defaults.
sll_validate_settingValidate a module setting. Receives prior result, key, submitted value, and settings service.

Shared actions

ActionWhen it runs
sll_loadedServices are ready. Receives settings and authentication services.
sll_account_loadedA verified directory entry resolves to a WordPress user. Receives user and entry. It can run outside an interactive login.
sll_auth_successVerified LDAP password or server SSO authentication reaches a new or existing account. Receives the user. Use WordPress wp_login to observe completed WordPress logins.
sll_auth_failureLDAP password authentication fails.
sll_settings_savedSettings are saved. Receives settings service and before/after arrays.

Pro hooks

sll_user_meta_data filters custom metadata values before storage. sll_pro_groups adds groups needed by Pro role or membership rules.

Pro actions include sll_sso_failed, sll_profile_update, sll_import_finished, sll_account_imported, sll_access_check_failed, sll_access_changed, and sll_membership_changed. These report results from the matching feature. Review the source signatures before you attach a callback.

Settings screen hooks

sll_settings_tabs filters the tab names. sll_settings_notices adds notices. To add content, use sll_access_settings, sll_profile_settings, or sll_advanced_settings. Each receives the admin form service.

For a new tab, sll_settings_tab_{tab} adds content inside the standard settings form. sll_settings_page_{tab} supplies a complete page instead. Add defaults and validation for new settings, and keep WordPress permission and request checks in place.

Compatibility limits

A compatibility class provides the old global object and its settings methods. The old adLDAP object and directory administration methods are no longer available. The settings option remains sll_settings.

Directory login requires a unique verified user, a valid password or trusted server identity, and permitted groups. Keep those checks at the directory boundary. Do not call a remote license service during login; the plugin reads the saved status.

These hooks run locally. They do not send data to an external service by themselves.