[littlegrasscao]

Summary

• RecipientTokenDecorator authenticates sharing protocol requests by recipient bearer token: only activated, unexpired token hashes are accepted, and anything else is 401 with WWW-Authenticate: Bearer
• OpenSharing protocol List Shares: GET /shares lists one page of the shares the recipient holds SELECT on, ordered by name, using the core Pagination from server: page the provider list APIs #117
  • Pagination.protocolPage keeps the protocol's meaning of maxResults=0: no items, with a nextPageToken that resumes from the same position when any remain
• Get Share: GET /shares/{share} returns {"share": ...} for a granted share; a share the recipient holds no SELECT on is reported as not found
• both endpoints also match the Delta Sharing protocol's List Shares and Get Share
• the logic is framework-free in core (ProtocolShares, RecipientService.authenticate, and new SharePermissionStore and RecipientStore queries); OpenSharingProtocolService is a thin Armeria layer for the OpenSharing protocol's share, schema and table endpoints; the Delta Sharing table endpoints get their own DeltaSharingProtocolService (Delta Sharing protocol: query a shared Delta table version #105)
• OpenSharingRecipientApi.mount(...) serves the protocol and activation endpoints with their own JSON converters and error handling, so a host can mount them next to its own services. It takes the host's public URL, which profile files point recipients to. The standalone server now mounts activation through it

Testing

• mvn clean install: 132 tests passed
• OpenSharingProtocolServiceTest: a recipient authenticates with its activated token and lists only granted shares; missing, invalid, and superseded tokens are 401; shares page with opaque tokens, including many shares across pages, and maxResults=0 returns no shares with a token that resumes from the start
• ProtocolPaginationTest: a page size of 0 returns no items with a token to the same position, no token for an empty list, and other sizes page as provider lists do