fix(lumilake): accept lum.id lumid:admin scope so platform admins can submit jobs#9
Open
tjluyao wants to merge 1 commit into
Open
fix(lumilake): accept lum.id lumid:admin scope so platform admins can submit jobs#9tjluyao wants to merge 1 commit into
tjluyao wants to merge 1 commit into
Conversation
The PermissionPolicy admin_scopes ({lumilake:*, flowmesh:admin, ...}) never included
lum.id's actual platform-admin scope, lumid:admin. lum.id super_admin/admin PATs carry
lumid:read/write/admin (+ flowmesh:workflows:write) from /oauth/introspect — none of which
matched, so the kind-level lumilake:jobs:write gate rejected EVERY real caller and job
submission was impossible for any lum.id token. Add lumid:admin (mirrors the flowmesh:admin
rationale for shared platform admins). Verified end-to-end in the UKS deployment (job submit
403 -> 422).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The lumilake plugin's
PermissionPolicy.admin_scopeswas{"*","lumilake:*","lumilake:admin","flowmesh:admin"}. lum.id issues its platform-admin scope aslumid:admin(super_admin PATs carrylumid:read/write/admin+flowmesh:workflows:writefrom/oauth/introspect). None of those matched, so the kind-levellumilake:jobs:writegate inregister_resource(JOB, WRITE)rejected every lum.id caller — job submission was impossible for any real token, including super_admin.Fix
Add
lumid:admintoadmin_scopes(one line), mirroring the existingflowmesh:adminrationale for shared platform admins.Verification
Deployed to the UKS
lumid-prod2cluster (thin plugin layer on lumilake v0.1.3). Job submit went from 403 (lumilake:jobs:writerequired) to 422 (payload schema) with a super_admin PAT — i.e. auth/authz now pass. Also required a companion deploy-side fix (LUMID_DATA_TOKEN = a role=local key for the job-archive blob write); that one is deployment config, this is the source fix.🤖 Generated with Claude Code