Neo SPCC shipped updates across three NeoFS tools between Aug. 15 and 18: the REST Gateway, the web management Panel, and the Send.NeoFS file-sharing application. The releases remove deprecated authentication endpoints from the REST Gateway, introduce private file sharing in Send.NeoFS, and migrate Panel to the replacement auth API.

The updates follow a series of recent NeoFS infrastructure releases, including REST Gateway v0.18.0 in July and S3 Gateway v0.45.1 in early August, with both REST Gateway v0.19.0 and Panel v0.10.2 now updated to NeoFS SDK Go RC21 and NeoGo v0.122.0.

REST Gateway v0.19.0

The REST Gateway v0.19.0 release carries a breaking change: the deprecated /v1/auth and /v1/auth/bearer endpoints have been removed entirely. Applications relying on bearer token authentication through the REST Gateway must now use the /v2/auth/bearer and /v2/auth/bearer/complete endpoints instead. A migration guide is available in the repository.

Beyond the auth changes, the release adds the ability to specify extended access control lists during container creation. EACL defines who can access containers and objects in NeoFS, and provisioning workflows previously required creating a container first and then setting EACL as a separate operation. REST Gateway v0.19.0 combines both steps into a single request.

Object write buffering has also been optimized for improved upload performance, and ranged GET requests now use HTTP-alike NeoFS ranges for partial content retrieval. The update also improves Content-Disposition header handling for files with non-ASCII characters in their filenames. Associated Prometheus metrics for the removed auth v1 endpoints, auth_duration and form_binary_bearer_duration, have been dropped.

Send.NeoFS v0.7.0

Send.NeoFS v0.7.0, released Aug. 15, is the application’s first update in 16 months, following v0.6.6 in April 2025. The headline addition is private file sharing. Users can now send files to specific email-owned addresses using bearer tokens and extended access control lists. The bearer token grants GET access only when the requesting email matches the specified recipient, and a default EACL prohibits all other unauthorized retrieval attempts.

The release also fixes a bug that prevented uploading files with non-ASCII characters in their names, including Cyrillic and other international character sets. The non-ASCII filename improvement mirrors a similar fix in REST Gateway v0.19.0’s Content-Disposition handling, reflecting a broader effort to support international users across the NeoFS tool stack.

Send.NeoFS is a web application that demonstrates NeoFS integration via its HTTP protocol interface, and is live at send.fs.neo.org.

Panel v0.10.2

Panel v0.10.2, released Aug. 18, is a maintenance update prompted directly by the REST Gateway’s auth endpoint removal. The Panel, a React-based web interface for managing NeoFS containers, objects, and access control, has migrated from the deprecated /v1/auth endpoints to the /v2/auth/bearer API, adopting a simplified request structure that uses direct fields rather than array-wrapped payloads.

The Panel relies on the REST Gateway as its backend API bridge to NeoFS storage, making it a direct consumer of the auth endpoints. Its migration serves as a reference implementation of the auth v2 transition that all applications using the REST Gateway for bearer token generation will need to undertake. NNT previously covered Panel v0.10.1 as part of the NeoFS Node v0.55.0 and SDK RC21 release cycle in late July. Panel is live at panel.fs.neo.org.

The release notes for REST Gateway v0.19.0, Send.NeoFS v0.7.0, and Panel v0.10.2 can be found at the links below:

https://github.com/nspcc-dev/neofs-rest-gw/releases/tag/v0.19.0
https://github.com/nspcc-dev/send-fs-neo-org/releases/tag/v0.7.0
https://github.com/nspcc-dev/panel-fs-neo-org/releases/tag/v0.10.2

Tags: ,