Remove AD references with LDAP

Due to supporting mutliple LDAP server types, removal of AD specific documentation should be removed.

Author: stevebauman

docs/auth.md

@@ -634,16 +634,16 @@ class LdapAttributeHandler
 #### Password Synchronization
 
 The password sync option allows you to automatically synchronize
-users AD passwords to your local database. These passwords are
+users LDAP passwords to your local database. These passwords are
 hashed natively by laravel.
 
 Enabling this option would also allow users to login to their
-accounts using the password last used when an AD connection
+accounts using the password last used when an LDAP connection
 was present.
 
 If this option is disabled, the local user account is applied
 a random 16 character hashed password, and will lose access
-to this account upon loss of AD connectivity.
+to this account upon loss of LDAP connectivity.
 
 This feature is disabled by default.
 
@@ -670,27 +670,29 @@ There are several events fired during each operation that takes place in Adldap2
 The login fallback option allows you to login as a local database user using the default Eloquent authentication
 driver if LDAP authentication fails. This option would be handy in environments where:
 
-- You may have some active directory users and other users registering through the website itself (user does not exist in your AD).
-- Local development where your AD server may be unavailable
+- You may have some active directory users and other users registering through
+  the website itself (user does not exist in your LDAP directory).
+- Local development where your LDAP server may be unavailable
 
 To enable it, simply set the option to true in your `config/adldap_auth.php` configuration file:
 
 ```php
 'login_fallback' => env('ADLDAP_LOGIN_FALLBACK', true), // Set to true.
 ```
 
-#### Developing Locally without an AD connection
+#### Developing Locally without an LDAP connection
 
-You can continue to develop and login to your application without a connection to your AD server in the following scenario:
+You can continue to develop and login to your application without a
+connection to your LDAP server in the following scenario:
 
 * You have `auto_connect` set to `false` in your `adldap.php` configuration
- > This is necessary so we don't automatically try and bind to your AD server when your application boots.
+ > This is necessary so we don't automatically try and bind to your LDAP server when your application boots.
 
 * You have `login_fallback` set to `true` in your `adldap_auth.php` configuration
  > This is necessary so we fallback to the standard `eloquent` auth driver.
 
 * You have `password_sync` set to `true` in your `adldap_auth.php` configuration
- > This is necessary so we can login to the account with the last password that was used when an AD connection was present.
+ > This is necessary so we can login to the account with the last password that was used when an LDAP connection was present.
 
 * You have logged into the synchronized LDAP account previously
  > This is necessary so the account actually exists in your local app's database.
@@ -703,9 +705,9 @@ application without a persistent connection to your LDAP server.
 Model binding allows you to attach the users LDAP model to their Eloquent
 model so their LDAP data is available on every request automatically.
 
-> **Note**: Before we begin, enabling this option will perform a single query on your AD server for a logged
+> **Note**: Before we begin, enabling this option will perform a single query on your LDAP server for a logged
 in user **per request**. Eloquent already does this for authentication, however
-this could lead to slightly longer load times (depending on your AD
+this could lead to slightly longer load times (depending on your LDAP
 server and network speed of course).
 
 To begin, insert the `Adldap\Laravel\Traits\HasLdapUser` trait onto your `User` model:
@@ -757,7 +759,7 @@ in some other means with Apache. Adldap2 does not set this up for you. To enable
 https://www.iis.net/configreference/system.webserver/security/authentication/windowsauthentication/providers/add
 
 > **Note**: The WindowsAuthenticate middleware utilizes the `scopes` inside your `config/adldap.php` file.
-> A user may successfully authenticate against your AD server when visiting your site, but
+> A user may successfully authenticate against your LDAP server when visiting your site, but
 > depending on your scopes, may not be imported or logged in.
 
 To use the middleware, insert it on your middleware stack inside your `app/Http/Kernel.php` file:
@@ -803,5 +805,5 @@ authentication enabled, IIS will set the PHP server variable `AUTH_USER`. This v
 is usually equal to the currently logged in users `samaccountname`.
 
 The configuration array represents this mapping. The WindowsAuthenticate middleware will
-check if the server variable is set, and try to locate the user in your AD server
+check if the server variable is set, and try to locate the user in your LDAP server
 by their `samaccountname`.

docs/importing.md

@@ -83,7 +83,7 @@ php artisan adldap:import --no-log
 
 ### Delete
 
-The `--delete` (or `-d`) option allows you to soft-delete deactivated AD users. No users will
+The `--delete` (or `-d`) option allows you to soft-delete deactivated LDAP users. No users will
 be deleted if your User model does not have soft-deletes enabled.
 
 ```bash
@@ -92,7 +92,7 @@ php artisan adldap:import --delete
 
 ### Restore
 
-The `--restore` (or `-r`) option allows you to restore soft-deleted re-activated AD users.
+The `--restore` (or `-r`) option allows you to restore soft-deleted re-activated LDAP users.
 
 ```bash
 php artisan adldap:import --restore

docs/quick-start.md

@@ -66,7 +66,7 @@ This guide was created with the help of [@st-claude](https://github.com/st-claud
 
     *  Two files will be published inside your `config` folder, `adldap.php` and `adldap_auth.php`.
 
-10. Modify the `config/adldap.php` file for your AD server configuration.
+10. Modify the `config/adldap.php` and `config/adldap_auth.php` files for your LDAP server configuration.
 
 11. Run the command `php artisan make:auth` to scaffold login controllers and routes.
 

src/Commands/Console/Import.php

@@ -155,7 +155,7 @@ public function isLogging() : bool
 
     /**
      * Returns true / false if users are being deleted
-     * if their account is disabled in AD.
+     * if their account is disabled in LDAP.
      *
      * @return bool
      */
@@ -166,7 +166,7 @@ public function isDeleting() : bool
 
     /**
      * Returns true / false if users are being restored
-     * if their account is enabled in AD.
+     * if their account is enabled in LDAP.
      *
      * @return bool
      */
@@ -253,7 +253,7 @@ protected function save(User $user, Model $model) : bool
     }
 
     /**
-     * Restores soft-deleted models if their AD account is enabled.
+     * Restores soft-deleted models if their LDAP account is enabled.
      *
      * @param User  $user
      * @param Model $model
@@ -268,7 +268,7 @@ protected function restore(User $user, Model $model)
             $user->isEnabled()
         ) {
             // If the model has soft-deletes enabled, the model is
-            // currently deleted, and the AD user account
+            // currently deleted, and the LDAP user account
             // is enabled, we'll restore the users model.
             $model->restore();
 
@@ -281,7 +281,7 @@ protected function restore(User $user, Model $model)
     }
 
     /**
-     * Soft deletes the specified model if their AD account is disabled.
+     * Soft deletes the specified model if their LDAP account is disabled.
      *
      * @param User  $user
      * @param Model $model
@@ -298,7 +298,7 @@ protected function delete(User $user, Model $model)
             $user->isDisabled()
         ) {
             // If deleting is enabled, the model supports soft deletes, the model
-            // isn't already deleted, and the AD user is disabled, we'll
+            // isn't already deleted, and the LDAP user is disabled, we'll
             // go ahead and delete the users model.
             $model->delete();
 

src/Config/config.php

@@ -92,7 +92,7 @@
                 | Account Prefix
                 |--------------------------------------------------------------------------
                 |
-                | The account prefix option is the prefix of your user accounts in AD.
+                | The account prefix option is the prefix of your user accounts in LDAP directory.
                 |
                 | This string is prepended to authenticating users usernames.
                 |
@@ -105,7 +105,7 @@
                 | Account Suffix
                 |--------------------------------------------------------------------------
                 |
-                | The account suffix option is the suffix of your user accounts in AD.
+                | The account suffix option is the suffix of your user accounts in your LDAP directory.
                 |
                 | This string is appended to authenticating users usernames.
                 |
@@ -134,7 +134,7 @@
                 | Port
                 |--------------------------------------------------------------------------
                 |
-                | The port option is used for authenticating and binding to your AD server.
+                | The port option is used for authenticating and binding to your LDAP server.
                 |
                 */
 
@@ -190,7 +190,7 @@
                 | Administrator Username & Password
                 |--------------------------------------------------------------------------
                 |
-                | When connecting to your AD server, a username and password is required
+                | When connecting to your LDAP server, a username and password is required
                 | to be able to query and run operations on your server(s). You can
                 | use any user account that has these permissions. This account
                 | does not need to be a domain administrator unless you

src/Middleware/WindowsAuthenticate.php

@@ -70,7 +70,7 @@ public function handle(Request $request, Closure $next)
      */
     protected function retrieveAuthenticatedUser($username)
     {
-        // Find the user in AD.
+        // Find the user in LDAP.
         if ($user = $this->resolveUserByUsername($username)) {
             $provider = $this->auth->getProvider();
 
@@ -81,7 +81,7 @@ protected function retrieveAuthenticatedUser($username)
             } elseif ($provider instanceof DatabaseUserProvider) {
                 $credentials = $this->makeCredentials($user);
 
-                // Here we'll import the AD user. If the user already exists in
+                // Here we'll import the LDAP user. If the user already exists in
                 // our local database, it will be returned from the importer.
                 $model = Bus::dispatch(
                     new Import($user, $this->model(), $credentials)