Support OAuth 2.0 Authentication for Spotfire Copilot Connections

Description of the Idea

We would like to request native support for OAuth 2.0 authentication when users interact with Spotfire Copilot.

Ideally, when a user opens the Copilot Panel or attempts to send their first chat message, Spotfire should prompt the user to authenticate via an OAuth flow (e.g., popup or redirect) to obtain a Bearer Token.

This user experience should be very similar to how Spotfire currently handles OAuth authentication for Data Connections (such as the Snowflake connector), where the user must authenticate their identity before executing queries.

Why is this needed? (Use Case)

Many enterprise organizations have strict security policies that prohibit direct access to public LLM endpoints (like OpenAI or standard AWS Bedrock).

Instead, all AI traffic must be routed through internal secure API Gateways or proxy servers. To ensure robust access control and auditing, these intermediaries often require user-level OAuth 2.0 authentication (with Bearer Tokens passed in the HTTP header) rather than static API keys.