← All updates Databricks Update One-Pager Light version
databricks Platform · Updated Jun 2, 2025

Unity Catalog HTTP connections support OAuth User-to-Machine Per User…

Individual users can now use their own OAuth credentials to sign into external services when using a Unity Catalog HTTP connection.

Public Preview Open docs ↗release note ↗
What it does

Individual users can now use their own OAuth credentials to sign into external services when using a Unity Catalog HTTP connection. Previously, the only OAuth option was to share a single OAuth credential for the connection regardless of the user. Preview This feature is in Public Preview.

Why it matters

This approach is suitable for shared devices or environments where a consistent user identity is sufficient, but it reduces individual accountability and tracking.

Key capabilities
Bearer token: Obtain a bearer
Bearer token: Obtain a bearer token for simple token-based authentication.
Dynamic Client Registration (DCR): Automatically
Dynamic Client Registration (DCR): Automatically discover and register OAuth credentials using the RFC 7591 protocol. Each user…
OAuth 2.0 Machine-to-Machine: Create and
OAuth 2.0 Machine-to-Machine: Create and configure an app to enable machine-to-machine authentication.
OAuth 2.0 User-to-Machine Shared: Authenticate
OAuth 2.0 User-to-Machine Shared: Authenticate with user interaction to share access between service identity and machine.
Architecture
Databricks Platform → Platform
In short

Individual users can now use their own OAuth credentials to sign into external services when using a Unity Catalog HTTP connection. Previously, the only OAuth option was to share a single OAuth credential for the connection regardless of the user.

Read the full documentation ↗
Key takeaway
Individual users can now use their own OAuth credentials to sign into external services when using a Unity Catalog HTTP connection.
2025-06-02-629f34cd Generated by the Databricks Updates Agent · browse all updates