Remove OAuth authorization flows and use API key authentication for MCP

This commit is contained in:
Mike Cao committed 2026-09-09 15:22:15 -07:00
1 parent 16acac5530
commit b185837063
85 files changed
+383 -4631

No files matched your search

+1 -10
View File
@@ -521,15 +521,6 @@
"two-factor-locked-message": "Too many failed attempts. Try again at {time}.",
"two-factor-active-description": "Your account is protected with two-factor authentication. Each login requires a code from your authenticator app.",
"api-key-created": "Copy your API key now. You won't be able to see it again.",
"no-api-keys": "You have not created any API keys.",
"oauth-login-prompt": "Sign in to continue.",
"oauth-consent": "{name} wants to access your Umami account.",
"oauth-permissions": "This will allow the application to:",
"oauth-scope-websites-read": "See the websites you have access to",
"oauth-scope-analytics-read": "Read analytics data for those websites",
"oauth-redirect-notice": "After you approve, you will be sent to {url}.",
"oauth-signed-in-as": "Signed in as {username}",
"oauth-invalid-request": "This authorization request is invalid.",
"oauth-redirecting": "Redirecting…"
"no-api-keys": "You have not created any API keys."
}
}