chore: remove unused audience field from AccessToken - #32783
chore: remove unused audience field from AccessToken#32783detail-app[bot] wants to merge 1 commit into
Conversation
|
Hi there 👋 Thanks for your contribution! The OpenMetadata team will review the PR shortly! Once it has been labeled as Let us know if you need any help! |
✅ Playwright Results — workflow succeededValidated commit ✅ 557 passed · ❌ 0 failed · 🟡 0 flaky · ⏭️ 0 skipped · 🧰 0 lifecycle flaky PerformanceBlocking targets: ✅ met · Optimization targets: 🟡 in progress Shard-job maxima below are not the full workflow wall time; the linked run includes build, fixture, planning, and reporting. 🕒 Full workflow signal wall (to summary) 48m 35s ⏱️ Max setup 4m 8s · max shard execution 19m 17s · max shard-job elapsed before upload 23m 5s · reporting 4s 🌐 234.62 requests/attempt · 2.82 app boots/UI scenario · 30.68% common-shard skew Optimization targets still in progress:
How to debug locally# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip # view trace |
Removed the
audiencefield, the 5-argAccessTokenconstructor,getAudience(), andsetAudience()fromopenmetadata-mcp/.../auth/AccessToken.java(19 lines). No callersexist anywhere in the codebase (production or test): the 5-arg
constructor is never invoked,
audienceis never read or written,and
OAuthTokenRepositoryneither persists nor hydrates it — thefield is silently lost on every round-trip. The sibling
RefreshTokenclass's 5th constructor parameter is
userName, notaudience, sothis is not a parallel-class convention.
History
Dead Code PRs can be configured here.