> ## 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).

# Logging in to Developer Console as a Service owner

> Logging in to Developer Console as a service owner using API Key and API secret parameters to access additional settings and functionalities.

A service owner can log in to its client application developer console by entering following parameters.

| Item | Parameter to be input |
| - | - |
| Login ID | API Key of the service |
| Password | API secret of the service |

When logging in to the console with the service's API key and secret, the service owner will be able to access additional parameters as is shown below.\\

<img src="https://mintcdn.com/authlete/U3PPUFJR_QzOnNDC/v2/deployment-and-operations/developer-console/client_setting_extension_en.png?fit=max&auto=format&n=U3PPUFJR_QzOnNDC&q=85&s=380bf8732c958e86ee414b07d41af39c" alt="client_setting_extension_en" width="900" height="422" data-path="v2/deployment-and-operations/developer-console/client_setting_extension_en.png" />

*Additional parameters that only service owners can access*

Please refer to the following document when letting third-party client app developers to log in to the client application developer consoles.

/v2/deployment-and-operations/developer-console/developer-authentication-callback


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