From f292b12eec1c7b0d66931ce658bb96631beec603 Mon Sep 17 00:00:00 2001
From: Justin Spahr-Summers <justin@anthropic.com>
Date: Tue, 18 Feb 2025 10:20:33 +0000
Subject: [PATCH] Remove `generateToken` until needed

---
 src/server/auth/crypto.ts   | 5 -----
 src/server/auth/provider.ts | 2 --
 2 files changed, 7 deletions(-)
 delete mode 100644 src/server/auth/crypto.ts

diff --git a/src/server/auth/crypto.ts b/src/server/auth/crypto.ts
deleted file mode 100644
index 3946d1f8..00000000
--- a/src/server/auth/crypto.ts
+++ /dev/null
@@ -1,5 +0,0 @@
-import crypto from "node:crypto";
-
-export function generateToken(): string {
-  return crypto.randomBytes(32).toString("hex");
-}
\ No newline at end of file
diff --git a/src/server/auth/provider.ts b/src/server/auth/provider.ts
index 78da8bc4..7e4260a0 100644
--- a/src/server/auth/provider.ts
+++ b/src/server/auth/provider.ts
@@ -21,8 +21,6 @@ export interface OAuthServerProvider {
   /**
    * Begins the authorization flow, which can either be implemented by this server itself or via redirection to a separate authorization server. 
    * 
-   * An authorization code can be generated using the `generateToken` function.
-   * 
    * This server must eventually issue a redirect with an authorization response or an error response to the given redirect URI. Per OAuth 2.1:
    * - In the successful case, the redirect MUST include the `code` and `state` (if present) query parameters.
    * - In the error case, the redirect MUST include the `error` query parameter, and MAY include an optional `error_description` query parameter.