> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/a/authentication.md). # Authentication Authentication is the process of verifying the identity of a user, device, or system attempting to access a resource. It answers the question "who are you?" and typically involves presenting credentials such as a username and password, an API key, a token, or a certificate. Common authentication methods in API contexts include API keys, OAuth 2.0 tokens, JSON Web Tokens (JWT), and mutual TLS. Each method has different security characteristics and is suited to different use cases. API keys are simple but offer limited security, while OAuth 2.0 provides delegated authorization flows suitable for third-party access. API gateways commonly handle authentication as a centralized concern, validating credentials before requests reach backend services. This offloads authentication logic from individual services, ensures consistent enforcement, and simplifies the security architecture. In serverless deployments, gateway-level authentication is particularly important since there is no persistent server to maintain session state. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.serverlessapigateway.com/glossary/a/authentication.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.