databricks-isv-databricks-connect

Databricks Connect authentication for ISV integrations is automated by configuring a host, appropriate credentials like a PAT or OAuth client credentials, and a serverless_compute_id or cluster_id to establish a secure remote Spark execution session.

Remote Spark execution supports Personal Access Tokens (PAT), OAuth Machine-to-Machine (M2M), and OAuth User-to-Machine (U2M) authentication methods, enabling flexible and secure connections across multiple environments.

Yes, PWAF-compliant partner integrations support both serverless and classic compute for Databricks Connect sessions, requiring a serverless_compute_id or cluster_id alongside your host and credentials.

Telemetry for PWAF partner integrations is handled by applying the recommended userAgent pattern during session setup, ensuring consistent observability and tracking for remote Spark jobs.

To initialize a Databricks Connect session, you need a host, a token for PAT or client credentials for OAuth M2M, and a target serverless_compute_id or cluster_id to automate the secure setup.

Using OAuth M2M instead of PAT for ISV integrations provides automated, secure server-to-server authentication without manual token management, aligning with PWAF compliance for remote Spark execution.