Verifying the Username and Password against the Active Directory

There are cases where the Active Directory is used as an authentication server. The Username and Password can be passed from other Pipelines, Ultra, or Triggered Tasks. The following Pipeline verifies user credentials against an Active Directory and returns the details where the authentication result is success. Each entry that fails authentication, also contains the reason and suggested resolution for the error. The Pipeline drops the document when the username and password are not valid. For purposes of demonstration, the Mapper Snap in this Pipeline sets up a user's AD credentials into the output of the Snap for passing them to the Active Directory Authenticate Users Snap.



Download this Pipeline
  1. Configure the Mapper Snap to set up a user's AD credentials into the output of the Snap for passing them to the Active Directory Authenticate Users Snap. Configure the Mapper Snap to prepare a document input for the Authenticate Users Snap with credentials of multiple users, if it suits your requirements.
    Configuration Output




  2. Configure the Active Directory Authenticate Users Snap to capture the user credentials from the Mapper output and verify them against the LDAP server to which it is connecting.
    Configuration Output




    Note: In certain scenarios, the Snap may be unable to process the entire input due to limitations imposed by the endpoint's API. In such cases, select the Pass through checkbox to ensure that the unprocessed input is not lost. You can process the remaining input data using more of the same Snap in the Pipeline. Alternatively, you can also write the original data into a separate file using a combination of the Mapper Snap and the File Writer Snap.
  3. The Pipeline uses a Filter Snap to filter the document with a success authentication result (output from the Active Directory Authenticate Users Snap) and pass it into the downstream Snap. When the username or password is not valid, the Pipeline drops the document with the following response: result = fail.
    Configuration Output




After the authentication is complete, use other Snaps to suit your requirements. For example:

  • Query data from a SQL Server database using the SQL Server - Select Snap.
  • Forward the request to another service using the REST Post Snap.
To reuse the example pipelines:
  1. Download and import the SLP file into your Environment.
  2. Configure Snap accounts.
  3. Provide Pipeline parameters, if any.