[jeffspahr]

A successful MLMD ownership lookup can authorize an artifact even when its standard storage key explicitly names another namespace. For keys under the configured private-artifacts/<namespace>/ prefix, reject a mismatch with the caller's authorized namespace before consulting MLMD or reading storage. The check covers encoded namespace aliases and namespace directory roots in both direct and proxied artifact paths.

Custom roots without that prefix retain their existing metadata-based behavior. This is bounded protection for canonical keys; storage authority for custom roots remains separate work.

Verification: 59 focused validator and HTTP/protobuf integration tests passed. Frontend server lint, TypeScript typecheck, Prettier checks, and git diff --check passed. The integration test verifies that a tracked foreign-prefix object is denied before MLMD or object storage is contacted, while a matching-prefix object remains readable.

Signed-off-by: Jeff Spahr spahrj@gmail.com

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from jeffspahr. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

Contributor Report for @jeffspahr

Metric	Value
Kubeflow org member	Yes
Issues opened in kubeflow/pipelines	453
Merged PRs in kubeflow/pipelines	380
GitHub account age	3480 days (created 2017-04-21)
PR comments in kubeflow/pipelines	1635