Add OAuth 2.0 documentation

docs/oauth2.md

@@ -0,0 +1,241 @@
+---
+title: "OAuth 2.0 support"
+---
+
+Integrations that connect to cloud services often need to authenticate users via OAuth 2.0. Home Assistant provides a set of helpers in `homeassistant.helpers.config_entry_oauth2_flow` that handle the OAuth 2.0 flow, token storage, and token refresh lifecycle — so integrations don't have to implement this themselves.
+
+This page covers how to implement OAuth 2.0 in an integration, how to handle errors and best practices.
+
+Before reading this page, make sure you are familiar with [Application credentials](/docs/core/platform/application_credentials) and [Config entries](/docs/config_entries_index).
+
+## Overview
+
+Home Assistant's OAuth 2.0 helper provides:
+
+- A built-in Authorization Code flow via `config_entry_oauth2_flow`.
+- Automatic token refresh when an access token expires.
+- A session helper (`OAuth2Session`) for making authenticated API requests.
+- Error handling via a set of semantic exceptions
+
+The helper supports two credential approaches, both of which require `application_credentials` support.
+
+It's encouraged to use the built-in `config_entry_oauth2_flow` for standard Authorization Code flows. Use the existing template flows that inherit from `AbstractOAuth2FlowHandler`. As a last resort, only build own child flows if it's needed.
+
+## Supported OAuth 2.0 flows
+
+| Flow                         | Class                               | When to use                     |
+| ---------------------------- | ----------------------------------- | ------------------------------- |
+| Authorization code           | `LocalOAuth2Implementation`         | Standard browser-based flow     |
+| Authorization code with PKCE | `LocalOAuth2ImplementationWithPkce` | When the provider requires PKCE |
+| Custom                       | `AbstractOAuth2Implementation`      | Any non-standard flow           |
+
+## Implementing the config flow
+
+The integration's config flow must extend `AbstractOAuth2FlowHandler`:
+
+```python
+from homeassistant.helpers import config_entry_oauth2_flow
+
+
+class OAuth2FlowHandler(
+    config_entry_oauth2_flow.AbstractOAuth2FlowHandler, domain=DOMAIN
+):
+    """Handle the OAuth2 config flow."""
+
+    DOMAIN = DOMAIN
+
+    @property
+    def logger(self) -> logging.Logger:
+        """Return the logger."""
+        return logging.getLogger(__name__)
+
+    @property
+    def extra_authorize_data(self) -> dict[str, Any]:
+        """Return extra authorization parameters."""
+        return {
+            "scope": "access:offline",
+        }
+```
+
+The `extra_authorize_data` property is where you define the OAuth scopes and any other provider specific parameters required during the authorization request.
+
+### Reauthentication
+
+Home Assistant will refresh the access token when `async_ensure_token_valid` is called. However, if a token becomes permanently invalid (for example, if the user revokes access from the provider's website), Home Assistant will trigger a reauthentication flow. To support this, add `async_step_reauth` in your config flow:
+
+```python
+async def async_step_reauth(
+    self, entry_data: Mapping[str, Any]
+) -> ConfigFlowResult:
+    """Handle reauthentication."""
+    return await self.async_step_reauth_confirm()
+
+async def async_step_reauth_confirm(
+    self, user_input: dict[str, Any] | None = None
+) -> ConfigFlowResult:
+    """Confirm reauthentication."""
+    if user_input is None:
+        return self.async_show_form(step_id="reauth_confirm")
+    return await self.async_step_user()
+```
+
+## Making authenticated API requests
+
+Use `OAuth2Session` to make authenticated requests. It automatically injects a valid access token into each request and handles token refresh transparently.
+
+```python
+from homeassistant.helpers import config_entry_oauth2_flow
+
+session = config_entry_oauth2_flow.OAuth2Session(hass, entry, implementation)
+
+# The session handles token refresh, inside the library, when `async_ensure_token_valid` is called. This must be called before every request.
+await session.async_ensure_token_valid()
+response = await session.async_request("GET", "https://api.example.com/data")
+```
+
+
+- `async_ensure_token_valid` - refreshes the token if needed but does **not** return the token. This needs to done before every request to ensure there's a valid token. The token can be obtained from the `OAuth2Session.token` property.
+
+See [Error handling](#error-handling) below for how to handle errors during token requests.
+
+## Error handling
+
+When a token request or refresh fails, the OAuth 2.0 helper raises one of three exceptions defined in `homeassistant.helpers.config_entry_oauth2_flow`:
+
+| Exception                          | HTTP status          | Meaning                                                                          |
+| ---------------------------------- | -------------------- | -------------------------------------------------------------------------------- |
+| `OAuth2TokenRequestReauthError`    | 400–499 (except 429) | Non-recoverable. The token is invalid and the user must reauthenticate.          |
+| `OAuth2TokenRequestTransientError` | 500+ and 429         | Transient. The server is temporarily unavailable or rate-limited. Safe to retry. |
+| `OAuth2TokenRequestError`          | Base class           | Catch-all for token request failures not covered by the above two.               |
+
+All three exceptions inherit from `aiohttp.ClientResponseError` for backwards compatibility, but integrations should migrate to catching the new exceptions directly.
+
+### Integrations using the Data Update Coordinator
+
+If your integration uses the [Data Update Coordinator](/docs/integration_fetching_data/#coordinated-single-api-poll-for-data-for-all-entities), no special error handling is required. The coordinator automatically maps the new exceptions to the correct behavior:
+
+- `OAuth2TokenRequestReauthError` raises `ConfigEntryAuthFailed`, triggering a reauthentication flow
+- `OAuth2TokenRequestTransientError` treated as `UpdateFailed`, triggering the coordinator's retry mechanism
+
+### Integrations without a Data Update Coordinator
+
+If your integration does **not** use a coordinator, you must handle the exceptions explicitly wherever you call `async_get_access_token()` or `async_ensure_token_valid()`:
+
+```python
+from homeassistant.helpers.config_entry_oauth2_flow import (
+    OAuth2TokenRequestError,
+    OAuth2TokenRequestReauthError,
+    OAuth2TokenRequestTransientError,
+)
+from homeassistant.exceptions import ConfigEntryAuthFailed, ConfigEntryNotReady
+
+try:
+    await session.async_get_access_token()
+except OAuth2TokenRequestReauthError as err:
+    raise ConfigEntryAuthFailed(
+        translation_domain=DOMAIN,
+        translation_key="reauth_required",
+    ) from err
+except (OAuth2TokenRequestTransientError, OAuth2TokenRequestError) as err:
+    raise ConfigEntryNotReady(
+        translation_domain=DOMAIN,
+        translation_key="auth_server_error",
+    ) from err
+```
+
+## Complete examples
+
+### With Data Update Coordinator
+
+Look at the [library guide](/docs/api_lib_auth) on authentication for more information on building guidelines. The following examples act merely as an example how to interlink a library with OAuth2.0 in the Data Update Coordinator.
+
+```python
+from homeassistant.helpers import config_entry_oauth2_flow
+from homeassistant.helpers.update_coordinator import DataUpdateCoordinator, UpdateFailed
+
+
+class ExampleCoordinator(DataUpdateCoordinator[MyData]):
+    """Coordinator for the Example integration."""
+
+    def __init__(
+        self,
+        hass: HomeAssistant,
+        entry: ConfigEntry,
+        session: config_entry_oauth2_flow.OAuth2Session,
+        client: LibraryClient
+    ) -> None:
+        """Initialize the coordinator."""
+        super().__init__(
+            hass,
+            logger=logging.getLogger(__name__),
+            name=DOMAIN,
+            update_interval=timedelta(minutes=30),
+        )
+        self.session = session
+        self.client = client
+
+    async def _async_setup(self) -> None:
+        """Setup the coordinator."""
+        try:
+            self.client = ExampleApiClient(session=session)
+        except ApiClientAuthenticationError as err:
+            raise ConfigEntryAuthFailed(f"Error authenticating with library: {err}") from err
+
+    async def _async_update_data(self) -> MyData:
+        """Fetch data from the API."""       
+        try:
+            return await client.async_get_data()
+        except ApiClientError as err:
+            raise UpdateFailed(f"Error communicating with API: {err}") from err
+```
+
+### Without Data Update Coordinator
+
+```python
+from homeassistant.helpers.config_entry_oauth2_flow import (
+    OAuth2Session,
+    OAuth2TokenRequestError,
+    OAuth2TokenRequestReauthError,
+    OAuth2TokenRequestTransientError,
+)
+from homeassistant.exceptions import ConfigEntryAuthFailed, ConfigEntryNotReady
+
+
+async def async_setup_entry(hass: HomeAssistant, entry: ConfigEntry) -> bool:
+    """Set up Example from a config entry."""
+    implementation = await config_entry_oauth2_flow.async_get_config_entry_implementation(
+        hass, entry
+    )
+    session = OAuth2Session(hass, entry, implementation)
+
+    try:
+        await session.async_ensure_token_valid()
+    except OAuth2TokenRequestReauthError as err:
+        raise ConfigEntryAuthFailed(
+            translation_domain=DOMAIN,
+            translation_key="reauth_required",
+        ) from err
+    except (OAuth2TokenRequestTransientError, OAuth2TokenRequestError) as err:
+        raise ConfigEntryNotReady(
+            translation_domain=DOMAIN,
+            translation_key="auth_server_error",
+        ) from err
+
+    hass.data.setdefault(DOMAIN, {})[entry.entry_id] = session
+    await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
+    return True
+```
+
+## Best practices
+
+- Never catch `aiohttp.ClientResponseError` directly. Use the new OAuth exception hierarchy instead. The compatibility shim will eventually be removed.
+- Use the Data Update Coordinator where possible. It handles token refresh errors automatically and reduces the amount of boilerplate in each integration.
+- Don't put token logic in entity classes. Token management belongs in `async_setup_entry` or the coordinator, not in individual entity `async_update` methods.
+- Always handle `OAuth2TokenRequestReauthError` explicitly in integrations that don't use a coordinator. Failing to do so means the user will never be prompted to reauthenticate.
+- Raise `ConfigEntryNotReady` for transient errors. Transient errors are temporary and should be retried. Raise `ConfgEntryAuthFailed` for non-recoverable errors.
+- Always implement reauthentication (`async_step_reauth`) in your config flow so Home Assistant can prompt the user to re-link their account.
+- Use `extra_authorize_data` to specify scopes and parameters required by the provider during authorization. This keeps your implementation clean and focused on the provider's requirements.
+
+## Reference
+
+- [Blog post: Changes in OAuth 2.0 helper error handling](https://developers.home-assistant.io/blog/2026/02/19/oauth-token-request-error-handling)

sidebars.js

@@ -144,6 +144,7 @@ module.exports = {
         "core/integration_diagnostics",
         "core/integration_system_health",
         "configuration_yaml_index",
+        "oauth2",
         "dev_101_services",
         "creating_platform_index",
         "creating_component_generic_discovery",