auth

Coding rules for authentication in a Tableau server application, covering middleware order and three supported authentication paths.

In plain words
What is it for?
Use it when changing passthrough authentication, embedded OAuth with PKCE, Tableau Cloud OAuth, token validation, session caching, or authentication middleware.
Why use it?
It keeps authentication changes consistent with how sessions, OAuth tokens, scopes, and request handling work in the application.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/tableau/tableau-mcp/auth
Clone the repo
git clone --depth 1 https://github.com/tableau/tableau-mcp

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 878 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00878
Opus 5 $0.00000 $0.00439
Sonnet 5 $0.00000 $0.00176
Haiku 4.5 $0.00000 $0.00088

Measured yesterday against content hash 8d49ceb6fc28, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

auth scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

  • auth — 100% identical, 0 lines differ
  • auth — 100% identical, 0 lines differ
  • auth — 100% identical, 0 lines differ
.cursor/rules/auth.mdc · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Auth Standards

Three Auth Paths

1. Passthrough Auth

  • Header x-tableau-auth or cookie workgroup_session_id
  • Validated via RestApi.authenticatedServerMethods.getCurrentServerSession()
  • Optional session caching via ExpiringMap (configurable interval)
  • Location: src/server/passthroughAuthMiddleware.ts
  • Enabled when config.enablePassthroughAuth is true
  • MCP scopes NOT enforced (no way to verify original token scopes)

2. Embedded OAuth (PKCE)

  • JWE-encrypted MCP access tokens signed with server's private key
  • Contains embedded Tableau access/refresh tokens
  • EmbeddedAccessTokenValidator validates via jose
  • Location: src/server/oauth/provider.ts, accessTokenValidator.ts, token.ts, authorize.ts, callback.ts

3. Tableau Cloud OAuth

  • Tableau Cloud JWT Bearer tokens
  • TableauAccessTokenValidator validates JWT claims
  • Location: src/server/oauth/provider.ts, accessTokenValidator.ts

Middleware Chain Order (express.ts)

handlePingRequest
  → passthroughAuthMiddleware (if enabled)
    → oauthProvider.authMiddleware
      → validateProtocolVersion
        → createMcpServer

Auth Info Flow

req.auth
  → getTableauAuthInfo(req.auth)
    → TableauAuthInfo (discriminated union: 'X-Tableau-Auth' | 'Bearer' | 'Passthrough')
      → TableauRequestHandlerExtra.tableauAuthInfo
        → useRestApi() (handles sign-in, token setup, sign-out lifecycle)

TableauAuthInfo Type (src/server/oauth/schemas.ts)

Discriminated union on type field:

  • 'X-Tableau-Auth' — username, server, siteId?, userId?, accessToken?, refreshToken?
  • 'Bearer' — username, server, siteId, userId?, raw (the JWT string)
  • 'Passthrough' — username, userId, server, siteId, raw (the session token)

REST API Auth Lifecycle (src/restApiInstance.ts)

useRestApi() is the single entry point for all authenticated API calls:

  • Creates a fresh RestApi instance per call
  • Routes to correct auth method based on tableauAuthInfo.type and config.auth
  • Auth methods: pat, direct-trust, uat, oauth
  • PAT/direct-trust sessions are ephemeral (signed out after use)
  • OAuth/passthrough sessions are long-lived (NOT signed out)
  • Accepts jwtScopes for direct-trust/UAT token generation

Read the full file on GitHub · 87 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 87 lines · 0 tokens per session scan A 8d49ceb6fc28

Subscribe to this mod's changes

auth is a cursor rule published in the GitHub repository tableau/tableau-mcp (329 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 878 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other cursor rules, from other repositories

thing

Cursor rule "thing" from burugo/one-mcp, covering rule name: thing orm usage guide, description, core concept, configuration and basic usage.

burugo/one-mcp · 0 tokens

tdd

Final Verification: Always use: go test -v ./backend/api/handler/... | grep FAIL.

burugo/one-mcp · 0 tokens

language

Always respond in Chinese with utf-8 encoding. Git commit messages and code comments should always be in English. Remember, programs must be written for people to read, and only incidentally for machines to execute.

burugo/one-mcp · 56 tokens

mcp-framework

We are in the mcp-framework , a typescript framework that allows construction of model context protocol (mcp) servers. We are implementing the new specification: Overview MCP provides a standardized way for applications to.

QuantGeekDev/mcp-framework · 0 tokens

elysia

TITLE: Elysia Supported Schema Validation Types DESCRIPTION: Elysia provides declarative schema support for various parts of an HTTP request and response, enabling robust validation and automatic OpenAPI generation. SOURCE: https://github.com/elysiajs/documentation/blob/main/docs/essential/validation.md#snippet3.

kerlos/elysia-mcp · 0 tokens

mcp

TITLE: Implement Transport Error Handling in TypeScript and Python DESCRIPTION: This code snippet illustrates how to incorporate comprehensive error handling within transport implementations. It demonstrates catching exceptions during connection establishment and message transmission, logging errors, and ensuring…

kerlos/elysia-mcp · 0 tokens