auth jwt and update titles

Author: rpmccarter

settings/authentication-personalization/authentication/jwt.mdx

@@ -0,0 +1,102 @@
+---
+title: 'JWT Handshake'
+description: 'Use a customized login flow to authenticate users'
+---
+
+<Info>
+  This is the documentation for the JWT **Authentication** Handshake. The steps for setting up the [JWT **Personalization** Handshake](/settings/authentication-personalization/personalization/jwt) are slightly different.
+</Info>
+
+If you don’t have a dashboard, or if you want to keep your dashboard and docs completely separate, you can use your own login flow to authenticate users via a JWT in the URL.
+
+## Implementation
+
+<Steps>
+  <Step title="Generate a private key">
+    Go to your [Mintlify dashboard settings](https://dashboard.mintlify.com/mintlify/mintlify/products/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:
+    - Authenticate the user
+    - Create a JWT containing the authenticated user's info in the [UserInfo](../sending-data) format
+    - Sign the JWT with the secret key, using the EdDSA algorithm
+    - 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/mintlify/mintlify/products/authentication) and add the login URL to your User Auth settings.
+  </Step>
+</Steps>
+
+## Example
+
+I want to set up authentication for my docs hosted at `docs.foo.com`. I want my docs
+to be completely separate from my dashboard (or I don’t have a dashboard at all).
+
+To set up authentication with Mintlify, I go to my Mintlify dashboard and generate a
+JWT secret. I create a web URL `https://foo.com/docs-login` that initiates a login flow
+for my users. At the end of this login flow, once I have verified the identity of the user,
+I create a JWT containing the user’s custom data according to Mintlify’s specification.
+I use a JWT library to sign this JWT with my Mintlify secret, create a redirect URL of the
+form `https://docs.foo.com/login/jwt-callback#{SIGNED_JWT}`, and redirect the user.
+
+I then go to the Mintlify dashboard settings and enter `https://foo.com/docs-login` for the
+Login URL field.
+
+Here's what the code might look like:
+
+<CodeGroup>
+```ts
+import * as jose from 'jose';
+import { Request, Response } from 'express';
+
+const TWO_WEEKS_IN_MS = 1000 * 60 * 60 * 24 * 7 * 2;
+
+const signingKey = await jose.importPKCS8(process.env.MINTLIFY_PRIVATE_KEY, 'EdDSA');
+
+export async function handleRequest(req: Request, res: Response) {
+  const userInfo = {
+    expiresAt: Math.floor((Date.now() + TWO_WEEKS_IN_MS) / 1000), // 2 week session expiration
+    groups: res.locals.user.groups,
+    content: {
+      firstName: res.locals.user.firstName,
+      lastName: res.locals.user.lastName,
+    },
+  };
+
+  const jwt = await new jose.SignJWT(userInfo)
+    .setProtectedHeader({ alg: 'EdDSA' })
+    .setExpirationTime('10 s') // 10 second JWT expiration
+    .sign(signingKey);
+
+  return res.redirect(`https://docs.foo.com#${jwt}`);
+}
+```
+
+```python
+import jwt # pyjwt
+import os
+
+from datetime import datetime, timedelta
+from fastapi.responses import RedirectResponse
+
+private_key = os.getenv(MINTLIFY_JWT_PEM_SECRET_NAME, '')
+
+@router.get('/auth')
+async def return_mintlify_auth_status(current_user):
+  jwt_token = jwt.encode(
+    payload={
+      'exp': int((datetime.now() + timedelta(seconds=10)).timestamp()),    # 10 second JWT expiration
+      'expiresAt': int((datetime.now() + timedelta(weeks=2)).timestamp()), # 1 week session expiration
+      'groups': ['admin'] if current_user.is_admin else [],
+      'content': {
+        'firstName': current_user.first_name,
+        'lastName': current_user.last_name,
+      },
+    },
+    key=private_key,
+    algorithm='EdDSA'
+  )
+
+  return RedirectResponse(url=f'https://docs.foo.com/login/jwt-callback#{jwt_token}', status_code=302)
+```
+</CodeGroup>

settings/authentication-personalization/personalization/jwt.mdx

@@ -1,5 +1,5 @@
 ---
-title: 'JWT Auth'
+title: 'JWT Handshake'
 description: 'Use a customized login flow to authenticate users'
 ---
 
@@ -20,7 +20,7 @@ If you don’t have a dashboard, or if you want to keep your dashboard and docs
     Create a login flow that does the following:
     - Authenticate the user
     - Create a JWT containing the authenticated user's info in the [UserInfo](../sending-data) format
-    - Sign the JWT with the secret, using the EdDSA algorithm
+    - Sign the JWT with the secret key, using the EdDSA algorithm
     - Create a redirect URL back to your docs, including the JWT as the hash
   </Step>
   <Step title="Configure your User Auth settings">

settings/authentication-personalization/personalization/oauth.mdx

@@ -1,5 +1,5 @@
 ---
-title: 'OAuth 2.0'
+title: 'OAuth 2.0 Handshake'
 description: 'Integrate with your OAuth server to enable user login via the PKCE flow'
 ---
 

settings/authentication-personalization/personalization/shared-session.mdx

@@ -1,5 +1,5 @@
 ---
-title: 'Shared Session Auth'
+title: 'Shared Session Handshake'
 description: 'Seamlessly share user sessions between your dashboard and your docs'
 ---
 

settings/authentication-personalization/shared-features.mdx

@@ -3,12 +3,13 @@ title: 'Shared Features'
 description: 'A list of features offered by both Authentication and Personalization'
 ---
 
-Authentication can be thought of as Personalization + privacy, which means that all
-Personalization features are also Authentication features. This page will explain the
-different features of Personalization, all of which also apply to Authentication.
+Personalization refers to a suite of features that allow you to customize your
+documentation experience based on some information about the user. Authentication
+can be thought of as Personalization + privacy.
 
-Personalization allow you to identify your users so that you can personalize docs
-content for them. Example use cases:
+This page will explain the different features of Personalization, all of which
+are also available with Authentication. There are three major features of
+Personalization:
 
 - **Customize MDX content** with a user's information, such as their name, plan, or title.