Product preview
Authenticated upload
Release details
View changelog- Version
- v2
- Java
- 25
- Spring Boot
- 4.1.1
- License
- BuildBaseKit Commercial License
Capability summary
Features
The focused capabilities included in the current product generation.
Authenticated ownership
JWT-protected file operations are scoped to the authenticated owner. ROLE_ADMIN can list and operate on files across users.
LOCAL + S3-compatible storage
Store files on the local filesystem, AWS S3, MinIO, or another compatible S3 service behind one provider boundary.
Runtime storage administration
ROLE_ADMIN can inspect status, save LOCAL or S3 configuration, test connectivity, and explicitly select the active provider.
No silent fallback
When S3 is active and unavailable, the operation fails with a sanitized error instead of writing the file to LOCAL storage.
Per-file provider tracking
Each metadata row retains its provider. Switching affects new uploads; existing LOCAL and S3 files stay with their original provider.
Protected storage credentials
Database-backed S3 keys are encrypted with AES-256-GCM using an external master key, and API responses expose only presence flags.
Temporary access and thumbnails
LOCAL files use expiring application tokens, S3 uses pre-signed GET URLs, and PNG/JPEG uploads can produce protected JPEG thumbnails.
Defensive upload handling
Size, extension, MIME, and lightweight signature checks run before storage. UUID keys and path-containment checks avoid using client filenames as storage paths.
Developer-ready baseline
Java 25, Spring Boot 4.1.1, H2, MySQL, Flyway, the Maven wrapper, automated tests, Postman, and the /api-test workbench are included.
Fit
Who this is for
- Production applications that need authenticated, user-owned file APIs
- Teams operating LOCAL, AWS S3, MinIO, or another S3-compatible provider
- SaaS backends that need owner isolation with administrator access
- Projects that need controlled provider switching, temporary access, and thumbnails
Build or adopt
Why FiloraFS-Pro?
FiloraFS-Pro combines a focused identity layer, file ownership, persisted metadata, runtime provider administration, and delivery workflows in one Spring Boot file-storage foundation.
Without FiloraFS-Pro
- Design authentication, ownership, and role checks together
- Build and test LOCAL and S3-compatible provider operations
- Protect runtime provider credentials and switching workflows
- Persist metadata, temporary access, and thumbnail behavior
With FiloraFS-Pro
- JWT-protected owner and administrator workflows are connected
- The active provider controls new uploads without moving existing files
- Runtime configuration, connectivity tests, and explicit switching are included
- Temporary access, thumbnails, tests, Postman, and browser tooling are documented
Implementation resources
Technical documentation
Task-oriented setup, configuration, architecture, and API references for this product.
Run FiloraFS-Pro v2 with H2 and LOCAL storage, then verify its authenticated owner-scoped file APIs.
DocumentationStorageManage FiloraFS-Pro v2 LOCAL and S3-compatible providers, encrypted credentials, explicit switching, temporary access, and thumbnails.
DocumentationAPI ReferenceReference FiloraFS-Pro v2 authentication, owner-scoped file, user, temporary-access, and admin storage endpoints.
DocumentationConfigurationConfigure FiloraFS-Pro v2 persistence, JWT, LOCAL files, validation, workbench access, and encrypted runtime S3 settings.
DocumentationArchitectureUnderstand FiloraFS-Pro v2 identity, ownership, metadata, storage delegation, provider tracking, and secure runtime configuration.
Commercial terms
License, support, and updates
Review the maintained policies and release record before purchasing or updating the product.
Related guidance
Related guides
Architecture and implementation guidance related to this foundation.
Design a Spring Boot S3 upload flow with validation, storage boundaries, metadata, private objects, and pre-signed access where the workflow requires it.
GuideS3 Pre-Signed URLs in Spring BootGenerate short-lived Amazon S3 pre-signed URLs in Spring Boot after application authorization, while keeping buckets private and credentials on the server.
GuideProduction-Ready Spring Boot File Upload ArchitectureDesign a Spring Boot file upload system around validation, authorization, storage abstraction, metadata, delivery, cleanup, observability, and deployment responsibilities.
Get FiloraFS-Pro
Use FiloraFS-Pro when your application needs authenticated ownership, persisted metadata, and explicitly managed LOCAL or S3-compatible storage.