> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aihubmix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Choosing a Handshake

> How to decide which Handshake method is right for your docs

<Info>
  This is the documentation for **Authentication** Handshake methods. Personalization offers a [different set of Handshake methods](/settings/authentication-personalization/personalization-setup/choosing-a-handshake).
</Info>

Before your users can access personalized content, they must be authenticated. Mintlify supports four Authentication Handshake methods:

1. **Password**: Configure a set of global passwords for your documentation site.
2. **JWT**: Use your own login flow to authenticate your users via a JWT in the URL.
3. **OAuth 2.0**: Integrate with your OAuth server to enable user login via the standard Authorization Code flow.
4. **Mintlify Dashboard**: Allow all of your dashboard users to access your docs, zero configuration required.

## Prerequisites

<Tabs>
  <Tab title="Password">
    * Your security requirements allow for password sharing between documentation readers.
  </Tab>

  <Tab title="JWT">
    * You have some existing login flow.
    * You can add a final step in this login flow that creates a JWT and redirects to the docs.
  </Tab>

  <Tab title="OAuth 2.0">
    * You have an existing OAuth server that supports the Authorization Code flow.
    * You can create a new API endpoint that can be accessed by the returned OAuth access token.
  </Tab>

  <Tab title="Mintlify Dashboard">
    * Your documentation readers are also your documentation editors.
  </Tab>
</Tabs>

## Pros & Cons

<Tabs>
  <Tab title="Password">
    Pros:

    * Super simple setup
    * No configuration required for adding new users - just share the password

    Cons:

    * Difficult to revoke access to your docs without resetting the password
    * Lose personalization features, as there is no way to differentiate users with the same password
  </Tab>

  <Tab title="JWT">
    Pros:

    * Reduced risk of API endpoint abuse
    * Zero CORS configuration
    * No restrictions on API URLs

    Cons:

    * Must be able to hook into your existing login flow
  </Tab>

  <Tab title="OAuth 2.0">
    Pros:

    * Heightened security standard

    Cons:

    * Requires significant work if setting up OAuth server for the first time
    * Might be overkill for some applications
  </Tab>

  <Tab title="Mintlify Dashboard">
    Pros:

    * Zero-config setup

    Cons:

    * Requires all docs readers to have an account in your Mintlify dashboard
  </Tab>
</Tabs>