​

PAM Authentication

PAM integration validates proxy users against the system’s Pluggable Authentication Modules (PAM) stack. This allows you to use a single set of credentials for both OS-level access (SSH, Login) and proxy access.

​

When to use PAM Authentication

:::note Prerequisites

• SafeSquid running on a PAM-capable operating system (typically Linux).
• OS users and passwords already configured.
• Admin access to the SafeSquid Configuration Portal. :::

​

Enable PAM in Access Rules

1. Access Configuration: Open the Configuration Portal and click Configure.
2. Navigate to Allow List: Application Setup → Access Restrictions → Allow List.
3. Configure Rule:
   • Edit the entry that matches your client segment.
   • PAM Authentication: Set to TRUE.
   • Username/Password: Leave these empty (we are using OS PAM, not local SafeSquid credentials).
4. Save and Apply: Click the checkmark to save.

:::tip Note on Local Users If you create a user via useradd on the Linux host, SafeSquid will be able to authenticate them once PAM is set to TRUE. :::

​

Verification

​

Troubleshooting

​

Source register

​

Next steps

• Local Credential Store (BASIC) for SafeSquid-only users.
• Directory Services for enterprise identity integration.
• Bypass Authentication for services that cannot authenticate.