Skip to content

Conversation

@simonfaltum
Copy link
Member

When deployed in Databricks Apps, the platform injects an x-forwarded-access-token header containing the user's OAuth token. This change enables the chatbot to use this token for downstream API calls, allowing requests to execute with the user's identity and permissions.

Changes:

  • Modify provider fetch wrapper to use OBO token when Authorization header is present
  • Extract and pass OBO token in chat streaming and title generation endpoints
  • Send both Authorization: Bearer and x-forwarded-access-token headers for compatibility
  • Fall back to service principal/PAT/CLI auth when OBO header is absent
  • Update CLAUDE.md with OBO authentication documentation

When deployed in Databricks Apps, the platform injects an x-forwarded-access-token
header containing the user's OAuth token. This change enables the chatbot to use
this token for downstream API calls, allowing requests to execute with the user's
identity and permissions.

Changes:
- Modify provider fetch wrapper to use OBO token when Authorization header is present
- Extract and pass OBO token in chat streaming and title generation endpoints
- Send both Authorization: Bearer and x-forwarded-access-token headers for compatibility
- Fall back to service principal/PAT/CLI auth when OBO header is absent
- Update CLAUDE.md with OBO authentication documentation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant