> ## Documentation Index
> Fetch the complete documentation index at: https://developers.authlete.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> ### Authlete versions
> Authlete 3.0 is the current version. Unless the user says they use another version, answer for Authlete 3.0 using the 3.x documentation.
> Documentation for Authlete 2.x (pages under `/v2/` and `/ja/v2/`) is for the legacy version. Refer to it only when the user is on Authlete 2.x.
>
> ### Authlete architecture
> Authlete is a backend engine for OAuth 2.0 and OpenID Connect processing. End users and client applications do not call it directly; the service provider's authorization server and API server call Authlete's APIs. Authlete handles protocol processing and token, client, and service management, while the service provider owns the OAuth/OIDC endpoints and user authentication.
> See [Architecture](https://developers.authlete.com/get-started/introduction-to-authlete/architecture.md).
>
> ### Concepts
> If the user is new to Authlete, read these pages first:
> - [Request and Response](https://developers.authlete.com/get-started/concepts/request-and-response.md): Core API requests pass the client's request parameters as-is, and responses return `resultCode`, `action`, and `responseContent`.
> - [Action Handling](https://developers.authlete.com/get-started/concepts/action-handling.md): Branch on `action`, never on `resultCode`, and map each action to the HTTP response your server returns.
> - [Two-Step API Calls](https://developers.authlete.com/get-started/concepts/two-step-api-calls.md): Actions such as `INTERACTION` are completed with a second call (`/auth/authorization/issue` or `/auth/authorization/fail`) linked by a `ticket`.
> - [Management API Overview](https://developers.authlete.com/get-started/concepts/overview.md): The Management API configures services, manages clients, and operates issued tokens, separately from the protocol flows handled by the Core API.
> - [API Authentication](https://developers.authlete.com/get-started/concepts/authentication.md): Authlete APIs use bearer tokens: a Service Access Token (one service) or an Organization Token (the whole organization).

# error_description の日本語化

> error_description の日本語化方法について述べられています。

# error\_description の日本語化

RFC 6749 で定義されている error\_description は、使える文字列が指定されています。\
[https://tools.ietf.org/html/rfc6749#section-5.2](https://tools.ietf.org/html/rfc6749#section-5.2)

よって、お客様に実装いただく認可サーバーにおいて、error\_description を日本語化した場合、厳密には仕様違反となってしまいます。

仕様に準拠しながら日本語化を行う方法としては、error\_uri を用いて間接的に日本語のエラーを示す方法があります。以下概略となります。1. error\_description を日本語化し、お客様の認可サーバー配下のWebページ等に掲載する
2\. 次に、Authlete API が返す error\_uri を上記ウェブサイトへのリンクに書き換える


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.