* security: scoped read-only token for filer metadata subscriptions
A token signed with jwt.filer_signing.subscribe.key names the subscribe
methods and the path prefixes its holder may see. mTLS peers and admin
tokens stay unrestricted. Internal subscribers attach an admin token
when both keys are configured.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: enforce subscription token scope on metadata streams
With jwt.filer_signing.subscribe.key set, SubscribeMetadata and
SubscribeLocalMetadata authorize the caller first. A scoped caller gets
a stream that sends only events whose paths are all under its prefixes,
filters batches, and never carries log file refs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: send an admin token on internal metadata subscriptions
Peer filers, metadata followers and the lifecycle reader attach an
admin token when the subscribe key is configured, so they keep the full
stream without mTLS.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* shell: add fs.meta.token to mint metadata subscription tokens
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: end scoped metadata subscriptions at token expiry
The scope now carries the token's exp. The scoped stream's context ends
at that time and the call returns Unauthenticated, so an open stream no
longer outlives its token.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer.sync: sign metadata subscriptions with the source cluster's key
MetadataFollowOption takes a FilerJwtProvider; filer.sync passes the
one loaded from -a.security or -b.security, so clusters with different
admin keys both accept the subscription.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* shell: report fs.meta.token flag errors
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: give scoped metadata subscribers their own client id
A scoped caller could reuse another subscriber's ClientId with a higher
epoch and replace that registration, disconnecting it. Scoped streams now
register under a server-chosen id that no other subscriber holds.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* security: accept only HS256 metadata subscription tokens
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* security: test HS384 metadata subscription token rejection
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: never let a scoped subscriber replace another registration
The server-chosen id can be taken by another subscriber between choosing
and registering it. Registering scoped streams with the lowest epoch makes
addClient refuse them rather than replace the other registration.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: send position markers for events a scoped token withholds
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: test a scoped stream withholding a whole event batch
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: filter SendMsg on scoped metadata streams
The scoped wrappers only overrode Send, so a SendMsg on the embedded
stream would reach the client unfiltered. Route it through the same
filter and refuse any other message type. Ported from #12790.
Co-authored-by: mindaeon <30555587+mindaeon@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: test a scoped subscription through the real subscribe loop
Run SubscribeLocalMetadata with a scoped token over a flushed backlog,
the in-memory tail and live events: only in-scope events arrive, sibling,
"..", encoded and cross-boundary rename paths are dropped, and no log
file references are sent although the client asks for them. Without the
subscribe key every event still arrives. Ported from #12790.
Co-authored-by: mindaeon <30555587+mindaeon@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: test that the HTTP API refuses metadata subscription tokens
GET, HEAD, PUT, POST and DELETE all refuse a subscription token, also
when the subscribe key equals the read or write key. Ported from #12790.
Co-authored-by: mindaeon <30555587+mindaeon@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: mindaeon <30555587+mindaeon@users.noreply.github.com>
see https://blog.aqwari.net/xml-schema-go/
1. go get aqwari.net/xml/cmd/xsdgen
2. Add EncodingType element for ListBucketResult in AmazonS3.xsd
3. xsdgen -o s3api_xsd_generated.go -pkg s3api AmazonS3.xsd
4. Remove empty Grantee struct in s3api_xsd_generated.go
5. Remove xmlns: sed s'/http:\/\/s3.amazonaws.com\/doc\/2006-03-01\/\ //' s3api_xsd_generated.go