> ## Documentation Index
> Fetch the complete documentation index at: https://openmetadata-docs-release-watchers.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# OpenMetadata Chrome Extension | Official Documentation

> Install the browser extension to explore metadata and documentation directly while navigating your data tools.

# OpenMetadata Chrome Extension

The OpenMetadata Chrome Extension brings your metadata into any tool you're working in. Instead of switching tabs to look something up in OpenMetadata, you can view an asset's details directly from your browser.

## Installation

1. **Install the Extension**: Add the [OpenMetadata Chrome Extension](https://chromewebstore.google.com/detail/openmetadata/pakbbdhbbiclnceabdmnghamabjloofc) from the Chrome Web Store.

   <img src="https://mintcdn.com/openmetadata-docs-release-watchers/gLX8kqdmH3-5QCwO/public/images/how-to-guides/user-guide-for-data-stewards/openmetadat-chrome-extension.png?fit=max&auto=format&n=gLX8kqdmH3-5QCwO&q=85&s=54c50b054f6220fcbabfd278c0189a20" alt="OpenMetadata Chrome Extension in the Chrome Web Store" width="2364" height="1644" data-path="public/images/how-to-guides/user-guide-for-data-stewards/openmetadat-chrome-extension.png" />

2. **Pin to Chrome Browser**: Pin the extension to your Chrome toolbar so it's always one click away.

   <img src="https://mintcdn.com/openmetadata-docs-release-watchers/gLX8kqdmH3-5QCwO/public/images/how-to-guides/user-guide-for-data-stewards/pin-openmetadata-extension.png?fit=max&auto=format&n=gLX8kqdmH3-5QCwO&q=85&s=c6488ff5aa4934bd47ccfcec54c39cca" alt="Pinning the OpenMetadata extension in the Chrome toolbar" width="2594" height="926" data-path="public/images/how-to-guides/user-guide-for-data-stewards/pin-openmetadata-extension.png" />

3. **Connect to your Instance**: Click the **OpenMetadata** icon, enter the base URL of your OpenMetadata instance, and sign in.

   <img src="https://mintcdn.com/openmetadata-docs-release-watchers/gLX8kqdmH3-5QCwO/public/images/how-to-guides/user-guide-for-data-stewards/connect-instance.png?fit=max&auto=format&n=gLX8kqdmH3-5QCwO&q=85&s=04465fbe676e1d9ba81d7071717061e8" alt="Connecting the OpenMetadata extension to your instance" width="2496" height="1264" data-path="public/images/how-to-guides/user-guide-for-data-stewards/connect-instance.png" />

## What You Can Do

After you're signed in, the extension shows your **Activity Feeds** from the **My Data** page.

While working in a third-party tool that's integrated with OpenMetadata, click the extension to view the metadata for whatever you're looking at, including:

* Ownership
* Description
* Tags and glossary terms
* Schema
* Lineage
* Custom properties and more

## Single Sign-On (SSO) Configuration

If your OpenMetadata instance uses Single Sign-On (SSO), the extension's redirect URI must be registered as a **trusted redirect URI**. OpenMetadata validates login redirects against an exact-match allowlist, so any URI that isn't registered is rejected with a `400 Bad Request` and the extension can't complete sign-in.

The redirect URI follows this pattern, where `<extension-id>` is the ID of your installed extension:

`https://<extension-id>.chromiumapp.org/auth0`

For the OpenMetadata Chrome Extension published on the Chrome Web Store, this is:

`https://pakbbdhbbiclnceabdmnghamabjloofc.chromiumapp.org/auth0`

Register the redirect URI in one of two ways.

### Option 1: Configure in the UI

1. Go to **Settings** > **SSO**.

   <img src="https://mintcdn.com/openmetadata-docs-release-watchers/gLX8kqdmH3-5QCwO/public/images/how-to-guides/user-guide-for-data-stewards/access-sso.png?fit=max&auto=format&n=gLX8kqdmH3-5QCwO&q=85&s=c8fb66bd1b494f63c35dee322e8560ac" alt="Access SSO" width="3004" height="1674" data-path="public/images/how-to-guides/user-guide-for-data-stewards/access-sso.png" />

2. Select your provider and click **Configure**.

   <img src="https://mintcdn.com/openmetadata-docs-release-watchers/gLX8kqdmH3-5QCwO/public/images/how-to-guides/user-guide-for-data-stewards/select-provider.png?fit=max&auto=format&n=gLX8kqdmH3-5QCwO&q=85&s=9fa01c2c6f3c48cd351a1aceb12f01fa" alt="Select provider" width="2554" height="1122" data-path="public/images/how-to-guides/user-guide-for-data-stewards/select-provider.png" />

3. In the **Additional Trusted Redirect Uris** field, add the extension redirect URI.

   <img src="https://mintcdn.com/openmetadata-docs-release-watchers/gLX8kqdmH3-5QCwO/public/images/how-to-guides/user-guide-for-data-stewards/additional-trusted-redirect-uris.png?fit=max&auto=format&n=gLX8kqdmH3-5QCwO&q=85&s=380fe053d482ef68c5945c5ae03e480a" alt="Adding the extension redirect URI under Additional Trusted Redirect Uris in SSO settings" width="1586" height="916" data-path="public/images/how-to-guides/user-guide-for-data-stewards/additional-trusted-redirect-uris.png" />

### Option 2: Configure via Environment Variable

Set the `AUTHENTICATION_ADDITIONAL_TRUSTED_REDIRECT_URIS` environment variable to a JSON array of redirect URIs:

```bash theme={null}
export AUTHENTICATION_ADDITIONAL_TRUSTED_REDIRECT_URIS='["https://<extension-id>.chromiumapp.org/auth0"]'
```

This maps to `authenticationConfiguration.additionalTrustedRedirectUris` in the server configuration. It applies to both OpenID Connect (OIDC) and SAML login flows, and no database migration is required.

For more information about SSO and redirect configuration, see [Enable Security](/v2.0.x/deployment/security).

<Note>
  Matching is **exact**—scheme, host, port, path, and query must all match. Wildcard hosts (for example, `*.chromiumapp.org`) are not supported by design, because that would let any browser extension receive an OpenMetadata token. The list defaults to empty (`[]`), so existing deployments are unchanged until you opt in.
</Note>