Skip to main content
Pangolin can forward user identity information to your backend applications through custom HTTP headers. This allows your applications to receive user details directly from the request headers, enabling integration with Pangolin’s authentication system. AI Gateway resources send the same headers to the upstream provider when the caller is a known user. See Identity Headers.
Forwarded headers are only available when using authentication methods that provide user identity information.

​
Supported Headers

Pangolin forwards the following headers to your backend when user identity is available:

​
Authentication Methods

​
Headers Available

These authentication methods provide user identity information and will include the forwarded headers:

Single Sign-On (SSO)

Full user identity information including username, email, and name.

Email-based One Time Passcode (OTP)

Only Remote-Email is provided, set to the whitelisted address the visitor authenticated with. Remote-User, Remote-Name, and Remote-Role are not available since there is no associated user account.

Shareable Links

Only available if the link was created with an associated user account. In that case, full user identity information is forwarded, the same as SSO. Links created without an associated user do not provide identity headers.

​
Headers Not Available

These authentication methods do not provide user identity information:

PIN Code

No user identity - only access control.

Password

No user identity - only access control.

​
AI Gateway

AI Gateway resources forward the same Remote-User, Remote-Email, Remote-Name, and Remote-Role headers to the upstream model API when Pangolin knows the user: An unattributed manual key authenticates without sending these headers. Details are in Identity Headers.