OAuth에서 영감을 받은 위임된 AI 액세스로 원시 API 키 공유 중지
hackernews
|
|
🏗️ 프레임워크
#ai 딜
#ai 보안
#aipassport
#anthropic
#api 키
#oauth
#openai
#위임 액세스
원문 출처: hackernews · Genesis Park에서 요약 및 분석
요약
현재 널리 사용되는 API 키 공유 방식의 보안 취약점을 해결하기 위해, OAuth 인증 방식에서 영감을 받은 위임된 액세스 모델이 주목받고 있습니다. 이 새로운 접근법은 사용자가 원본 API 키를 직접 공유하지 않고도 AI 에이전트나 타 애플리케이션에 특정 작업을 수행할 권한을 부여할 수 있게 합니다. 이는 키 탈취 및 남용 우려를 줄이고 권한 관리의 세분화를 가능하게 하여, 더 안전하고 통제된 AI 생태계를 구축하는 데 기여할 것으로 기대됩니다.
본문
OAuth-inspired delegated AI access — stop sharing raw API keys with every app that wants to use AI on your behalf. AIPassport is an exploratory reference implementation of a broker that sits between third-party applications and upstream AI providers. Instead of handing apps your raw API key, you grant them scoped, time-limited, revocable access through signed JWT tokens. The broker enforces permissions, proxies requests, and injects real credentials only at the point of the upstream call. Raw provider keys never leave the server. This is a reference implementation and a starting point for discussion — not a finished standard or production system. See Status & Limitations and Security Model for details. - A third-party app requests access to a specific AI provider, model, and capability - The user reviews and approves the request through a consent flow, setting scope and time limits - The broker issues a signed JWT — a short-lived delegated token that never contains the raw API key - The app sends requests through the broker using the token as a Bearer credential - The broker validates the token, checks scopes and usage caps, injects the real API key, and proxies the request upstream - The user can revoke access at any time — all associated tokens are instantly invalidated - Raw API keys stay server-side. Provider credentials are stored in environment variables and injected only at proxy time. - Delegated tokens are signed JWTs. Tokens carry embedded claims (grant ID, issuer, expiration) and are cryptographically verified on every request. - Access is scoped. Each grant specifies the provider, allowed models, capabilities, request caps, and budget limits. - Access is time-limited. Grants and tokens expire automatically. - Access is revocable. Revoking a grant cascade-invalidates all its tokens immediately. The reference implementation is built with Express, TypeScript, SQLite, and the jose JWT library. It includes a demo UI, upstream proxy support for OpenAI and Anthropic, and a test suite with 57 passing tests. See Getting Started to run it locally, or Architecture for the system design.
Genesis Park 편집팀이 AI를 활용하여 작성한 분석입니다. 원문은 출처 링크를 통해 확인할 수 있습니다.
공유