PAM Authentication For Access Server Users

Abstract

Access Server supports PAM authentication in Linux for managing user accounts. This topic provides you with the details.

Access Server supports many authentication systems: local, LDAP, RADIUS, SAML, and PAM.

These are the five supported authentication systems:

Local: The built-in, local authentication system.
LDAP: Lightweight Directory Access Protocol for querying user information from tools such as Active Directory, OpenLDAP, and others.
RADIUS: Remote Authentication Dial-in User Service protocol for authenticating remote users in a system such as JumpCloud, Okta, etc.
SAML: Security Assertion Markup Language using XML to transfer identity data from a system such as Azure AD, OneLogin, etc.
PAM: Pluggable Authentication Modules, a centralized authentication in Linux where you manage the user accounts in the server's operating system where you’ve installed Access Server.

This topic provides information about PAM authentication.

Using PAM authentication for Access Server VPN users

The PAM authentication method validates username/password pairs to allow user VPN connections. You create users from your Access Server's Linux command-line interface (CLI) and manage their permissions in the Admin Web UI or CLI.

PAM offers flexibility through the authentication modules to customize user authentication to your business needs. The authentication modules you detach are directed by you or the local system administrator. They are outside of Access Server, so take that into consideration for support.

We provide these basic tutorials:

In this section:

PAM Authentication For Access Server Users

Using PAM authentication for Access Server VPN users

Search results