> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources/supported-auth-types-for-custom-integrations/pluggable-authentication-mode-pam.md).

# Pluggable Authentication Mode (PAM)

## Overview

A pluggable authentication module (PAM) is a system that integrates multiple low-level authentication schemes into a high-level application programming interface (API). PAM allows programs that rely on authentication to be written independently of the underlying authentication scheme.

## Fields

<table><thead><tr><th width="194">Fields</th><th>Description</th></tr></thead><tbody><tr><td>PAM System </td><td>Opens a list of the supported existing PAM systems</td></tr><tr><td>PAM Endpoint </td><td>The path of the endpoint corresponds and retrieves the secret from the PAM system.</td></tr><tr><td>PAM Secret Auth Type </td><td>Select the supported method to integrate to any of the selected source systems. Authentication details of the Source system can be found in their respective documentation. For instance, ServiceNow supports Basic and OAuth as authentication methods.</td></tr></tbody></table>

For example, if you choose **Basic** authentication, you will need to fill in the JSON paths for the username and password based on the secret template. This will ensure that the Connector will extract the original username and password from the PAM system.z

<div align="left"><figure><img src="/files/RXT3iIFGYOTWzDtxDMa0" alt=""><figcaption></figcaption></figure></div>