add docs for oauth

Author: rpmccarter

advanced/user-auth/choosing-an-auth-method.mdx

@@ -7,6 +7,7 @@ Before your users can access personalized content, they must be authenticated. M
 
 1. **Shared Session**: Utilize the same session token used by your dashboard to authenticate users.
 2. **JWT**: Use your own login flow to send user info to your docs via a JWT in the URL.
+3. **OAuth 2.0**: Integrate with your OAuth server to enable user login via the PKCE flow.
 
 ## Prerequisites
 
@@ -23,10 +24,15 @@ Before your users can access personalized content, they must be authenticated. M
       - If your dashboard is at `*.foo.com`, your **docs** must be hosted at `foo.com` or `*.foo.com`
   </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 PKCE flow.
+    - You can create a new API endpoint that can be accessed by the returned OAuth access token.
+  </Tab>
 </Tabs>
 
 ## Pros & Cons
@@ -42,20 +48,34 @@ Before your users can access personalized content, they must be authenticated. M
     Cons:
 
     - Your docs will make a request to your backend, which may be undesirable
+    - You must have a dashboard that uses session authentication
+    - CORS configuration is usually required
   </Tab>
   <Tab title="JWT">
     Pros:
 
-    - No dashboard needed
     - Reduced risk of API endpoint abuse
     - Zero CORS configuration
+    - No restrictions on API URLs
 
     Cons:
 
-    - Must build new functionality around your existing login flow
+    - Must be able to hook into your existing login flow
     - Dashboard sessions and docs authentication are completely decoupled, so users will need to log in to your dashboard and your docs separately
     - Every time you want to refresh user data, your users must re-login to your docs
       - If your users' data changes frequently, you must require your users to log in frequently or risk having stale data in the docs
       - If your users' data rarely changes, this shouldn't be a problem
   </Tab>
+  <Tab title="OAuth 2.0">
+    Pros:
+
+    - Heightened security standard
+    - No restrictions on API URLs
+
+    Cons:
+
+    - Requires significant work if setting up OAuth server for the first time
+    - Dashboard sessions and docs authentication are completely decoupled, so users will need to log in to your dashboard and your docs separately
+    - Might be overkill for some applications
+  </Tab>
 </Tabs>

advanced/user-auth/jwt.mdx

@@ -9,7 +9,7 @@ If you don’t have a dashboard, or if you want to keep your dashboard and docs
 
 <Steps>
   <Step title="Generate a private key">
-    Go to your [Mintlify dashboard settings](https://dashboard.mintlify.com/settings/integrations) and generate a private key. Store this key somewhere secure where it can be accessed by your backend.
+    Go to your [Mintlify dashboard settings](https://dashboard.mintlify.com/mintlify/mintlify/settings/deployment/user-authentication) and generate a private key. Store this key somewhere secure where it can be accessed by your backend.
   </Step>
   <Step title="Create a login flow">
     Create a login flow that does the following:
@@ -19,7 +19,7 @@ If you don’t have a dashboard, or if you want to keep your dashboard and docs
     - Create a redirect URL back to your docs, including the JWT as the hash
   </Step>
   <Step title="Configure your User Auth settings">
-    Return to your [Mintlify dashboard settings](https://dashboard.mintlify.com/settings/integrations) and add the login URL to your User Auth settings.
+    Return to your [Mintlify dashboard settings](https://dashboard.mintlify.com/mintlify/mintlify/settings/deployment/user-authentication) and add the login URL to your User Auth settings.
   </Step>
 </Steps>
 

advanced/user-auth/oauth.mdx

@@ -0,0 +1,41 @@
+---
+title: 'OAuth 2.0'
+description: 'Integrate with your OAuth server to enable user login via the PKCE flow'
+---
+
+If you have an existing OAuth server that supports the PKCE flow, you can integrate with Mintlify for a seamless login experience.
+
+## Implementation
+
+<Steps>
+  <Step title="Create your Info API">
+    Create an API endpoint that can be accessed with an OAuth access token, and responds with a JSON payload following the [UserInfo](./sending-data) format. Take note of the scope or scopes required to access this endpoint.
+  </Step>
+  <Step title="Configure your User Auth settings">
+    Go to your [Mintlify dashboard settings](https://dashboard.mintlify.com/mintlify/mintlify/settings/deployment/user-authentication), select the OAuth option, and fill out the required fields:
+
+    - **Authorization URL**: The base URL for the authorization request, to which we will add the appropriate query parameters.
+    - **Client ID**: An ID for the OAuth 2.0 client to be used.
+    - **Scopes**: An array of scopes that will be requested.
+    - **Token URL**: The base URL for the token exchange request.
+    - **Info API URL**: The endpoint that will be hit to retrieve user info.
+  </Step>
+  <Step title="Configure your OAuth client">
+    Copy the Redirect URL listed in the [Mintlify dashboard settings](https://dashboard.mintlify.com/mintlify/mintlify/settings/deployment/user-authentication) and add it as an authorized redirect URL for your OAuth server.
+  </Step>
+</Steps>
+
+## Example
+
+I have an existing OAuth server that supports the PKCE flow. I want to set up authentication for my docs hosted at `foo.com/docs`.
+
+To set up authentication with Mintlify, I create an endpoint `api.foo.com/docs/user-info` which requires an OAuth access token with the `docs-user-info` scope, and responds with the user's custom data according to Mintlify’s specification.
+
+I then go to the Mintlify dashboard settings, navigate to the User Auth settings, select OAuth, and enter the relevant values for the OAuth flow and Info API endpoint:
+- **Authorization URL**: `https://auth.foo.com/authorization`
+- **Client ID**: `ydybo4SD8PR73vzWWd6S0ObH`
+- **Scopes**: `['docs-user-info']`
+- **Token URL**: `https://auth.foo.com/exchange`
+- **Info API URL**: `https://api.foo.com/docs/user-info`
+
+Finally, I copy the Redirect URL displayed in the dashboard settings and add it as an authorized redirect URL in my OAuth client configuration settings.

advanced/user-auth/shared-session.mdx

@@ -19,7 +19,7 @@ This method utilizes the session authentication info already stored in your user
       </Warning>
   </Step>
   <Step title="Configure your User Auth settings">
-    Go to your [Mintlify dashboard settings](https://dashboard.mintlify.com/settings/integrations) and add the API URL and your Login URL to your User Auth settings.
+    Go to your [Mintlify dashboard settings](https://dashboard.mintlify.com/mintlify/mintlify/settings/deployment/user-authentication) and add the API URL and your Login URL to your User Auth settings.
   </Step>
 </Steps>
 

mint.json

@@ -158,7 +158,8 @@
               "pages": [
                 "advanced/user-auth/choosing-an-auth-method",
                 "advanced/user-auth/shared-session",
-                "advanced/user-auth/jwt"
+                "advanced/user-auth/jwt",
+                "advanced/user-auth/oauth"
               ]
             },
             "advanced/user-auth/sending-data"