Repository navigation
v9.0.0-rc.1
Pre-releaseTable of Contents
Changes in 9.0.0-rc.1
Summary
- Security - Harden origin validation for embed mode delegated authentication: #12572
- Security - Restrict group member data to authorized users: #12573
- Security - Harden public link brute force protection: #12944
- Security - Bump grpc dependency: #13066
- Bugfix - Recover uploads stuck in processing when the blob commit fails: #733
- Bugfix - Record the acting user in the audit log's User field: #4789
- Bugfix - Purge revisions stored with whole-second timestamps: #11167
- Bugfix - Return the created user in the invitation response: #12467
- Bugfix - Fix missing labels and low-contrast elements across the web UI: #12526
- Bugfix - Fix share metadata corruption during concurrent share operations: #12621
- Bugfix - Return metadata client init errors from the settings store: #12680
- Bugfix - Sync the
.psecfile name when a password-protected folder is renamed: #12684 - Bugfix - Reject space images which are too large to be rendered: #12701
- Bugfix - Allow space managers to remove shares created by other users: #12705
- Bugfix - Release the quota of upload sessions with unreadable node metadata: #12739
- Bugfix - Open files whose name contains a hash or question mark: #12740
- Bugfix - Truncate long resource names instead of overlapping the next column: #12754
- Bugfix - Fix uploads stuck in processing with the s3ng storage driver: #12756
- Bugfix - Generate web timestamp by env/git log; make it buildable without .git: #12758
- Bugfix - Restarting the proxy service on error was causing panics: #12769
- Bugfix - Ignore write error after successful read: #12772
- Bugfix - Use light logo in light mode (with dark blue topbar): #12782
- Bugfix - Renaming a resource to its current name is a silent no-op: #12784
- Bugfix - Support Collabora Online 26.x in the ocis_full deployment example: #12794
- Bugfix - Fix shift-click range selection in the files list: #12804
- Bugfix - Search for usernames if memberUid is used for group membership: #12814
- Bugfix - Truncate long user names in the admin settings users list: #12816
- Bugfix - Stop logging every service re-registration: #12833
- Bugfix - Password protection is enforced in the "Shared via link" list: #12835
- Bugfix - Wrap long values in share and user details views: #12840
- Bugfix - Tell public link visitors the link is temporarily blocked: #12841
- Bugfix - Hide app menu items from anonymous public link visitors: #12842
- Bugfix - Admin-uploaded logo now overrides theme-specific logos: #12847
- Bugfix - Recover the login page after the current user was deleted: #12851
- Bugfix - Apply renewed access token in embed mode with delegated authentication: #12856
- Bugfix - Resolve Safe/Vault permalinks: #12881
- Bugfix - Deny Safe/Vault access to users without permission: #12884
- Bugfix - Cache LDAP instance mapper lookups: #12899
- Bugfix - Do not share vault resources with users who cannot access them: #12905
- Bugfix - Explain why an upload or a duplicate does not fit the space quota: #12943
- Bugfix - Correct introduction version for OCIS_LDAP_INSTANCE_MAPPER_CACHE_TTL: #12948
- Bugfix - Text and BMP file previews failed where libvips has no ImageMagick: #12961
- Bugfix - Unify when the maintenance banner clears: #12966
- Bugfix - Restoring an already-restored trash item now returns 404: #12969
- Bugfix - Do not allow credentials for wildcard CORS origins: #12983
- Bugfix - Stop endless redirect loop when vault MFA step-up fails: #12985
- Bugfix - Fixed low color contrast on disabled danger buttons: #12992
- Bugfix - Fixed low color contrast on nav and primary button hover states: #12993
- Bugfix - Fixed low color contrast on dropdown menu item hover text: #12994
- Bugfix - Fixed low color contrast on share permission dropdown hover text: #12995
- Bugfix - Fixed low color contrast on file name in editor topbar: #12997
- Bugfix - Fixed low color contrast on disabled danger button text: #12998
- Bugfix - Return a retryable 503 when the OIDC userinfo call fails transiently: #12999
- Bugfix - Fixed low color contrast on notification bell badge: #13000
- Bugfix - Open Safe permanent links from outside the Safe: #13001
- Bugfix - Fixed arrow-key navigation in the notification dropdown: #13002
- Bugfix - Notification bell now announces the unread count: #13003
- Bugfix - Added a keyboard shortcut to move focus out of the text editor: #13004
- Bugfix - Hide "Shared via link" when public sharing is disabled: #13005
- Bugfix - Fixed missing accessible name on button loading spinner: #13018
- Bugfix - Announce status messages to screen readers: #13024
- Bugfix - Keep keyboard focus on the trigger when a dropdown closes: #13025
- Bugfix - Announce autocomplete comboboxes correctly to screen readers: #13041
- Bugfix - Restore focus after changing the account language: #13045
- Bugfix - Stop endless redirect loop when admin settings MFA step-up fails: #13069
- Bugfix - Fix file and folder downloads in vault mode: #13097
- Bugfix - Fix the LDAP master-ID filter when the base filter is empty: #13100
- Bugfix - Stop logging "no user in context" for data gateway requests: #13101
- Bugfix - Show an error instead of "no deleted files" for inaccessible trash: #13105
- Bugfix - Fix AuthApp and basic auth requests with custom PROXY_USER_OIDC_CLAIM: #13107
- Change - Respect proxy environment variables for OIDC requests: #12703
- Change - Replace axios with the native fetch API in Web: #12910
- Change - Replace GRPC_MAX_CONNECTION_AGE with client keepalive: #13020
- Change - Remove the MFA session extension popup in vault mode: #13085
- Enhancement - Bump Reva version: #12051
- Enhancement - Ship ownCloud branding as the default login background: #12406
- Enhancement - Apply Kiteworks branding to the web theme: #12464
- Enhancement - Configurable Keycloak invitation actions and working ocis_full SMTP: #12467
- Enhancement - Close Collabora WOPI CheckFileInfo property gaps: #12593
- Enhancement - Add EPUB library: #12648
- Enhancement - Add "Undo" action to the delete success notification: #12650
- Enhancement - Use a more distinctive icon for the software license link: #12669
- Enhancement - Add Mermaid diagram editor: #12676
- Enhancement - Restrict personal drive information to the owner and admins: #12742
- Enhancement - Add a command to recalculate the treesize of a space: #12746
- Enhancement - Add TLS support for NATS store and registry connections: #12765
- Enhancement - Update app store repository: #12793
- Enhancement - Colour tag chips by tag name: #12892
- Enhancement - Add TLS support for the frontend stat cache store connection: #12931
- Enhancement - Clarify the NATS store TLS insecure options: #12941
- Enhancement - Inline images in the markdown editor: #12967
- Enhancement - Default 30-day expiration for vault shares: #12988
- Enhancement - Make the public share expiry janitor configurable: #13020
- Enhancement - The public link resolution flag added to PROPFIND: #13020
- Enhancement - Add a --timeout flag to the search index command: #13052
- Enhancement - Record tag changes in the audit log: #13054
Details
-
Security - Harden origin validation for embed mode delegated authentication: #12572
Hardened origin validation for the delegated authentication feature in Web's
embed mode. Deployments usingWEB_OPTION_EMBED_DELEGATE_AUTHENTICATIONshould
ensureWEB_OPTION_EMBED_DELEGATE_AUTHENTICATION_ORIGINis explicitly
configured. -
Security - Restrict group member data to authorized users: #12573
The groups API could return group membership details to callers who should not
have had access to it. Access to group member data is now properly restricted
based on the caller's permissions. -
Security - Harden public link brute force protection: #12944
We've hardened the brute force protection for password protected public links so
that failed password attempts are reliably counted and the rate limit is
consistently enforced. -
Security - Bump grpc dependency: #13066
We've bumped the grpc dependency to fix a vulnerability that could cause a
server panic when handling requests missing authority or Host headers. -
Bugfix - Recover uploads stuck in processing when the blob commit fails: #733
When the final blob commit failed after postprocessing, the node kept its
processingmarker with no retry and no timeout. Every download then returned
425 Too Early, the file could not be deleted, and its reserved size kept
counting against the quota.The commit is now retried with backoff. If it still fails, the node is reverted
to a recoverable failed state, which clears the processing marker and releases
the reserved quota. -
Bugfix - Record the acting user in the audit log's User field: #4789
The audit log's
Userfield is documented as the UID of the user performing the
action, but the file and folder converters filled it from the event'sOwner,
which reva does not set, so the field was empty on every upload, download, move,
delete, restore and version restore. Where an event did carry an owner,User
named the owner rather than the person acting, for example a share recipient
uploading into a shared folder. Space, user and group events hard-coded the
field to an empty string although every one of those events carries the actor.Useris now taken from the event'sExecutantfor all of these events. The
Ownerfield of file events is unchanged. The failed public-link access event
still has no actor and keeps an emptyUser.While adding tests for the user and group events, the group member added and
removed messages turned out to pass the user and group ids in the wrong order,
naming the group as the user and the user as the group; that is fixed too. -
Bugfix - Purge revisions stored with whole-second timestamps: #11167
The revisions purge command reported a clean storage when revisions were still
present. Revision filenames are the previous mtime formatted with
time.RFC3339Nano, which omits fractional seconds on a whole second. Names such
as.REV.1601-01-01T00:00:00Znever matched the purge pattern, so those
revisions stayed on disk.The matcher now treats the decimal point and fractional digits as optional.
Whole-second revisions and their.mpkand.mlockcompanions are discovered
and purged along with revisions that still carry a fractional timestamp. -
Bugfix - Return the created user in the invitation response: #12467
The invitations service created the guest account but returned the original
request body unchanged, so theinvitedUserrelation defined by the Graph
invitation response was always empty. Clients had no way to learn the identity
of the user that was just created. The service now populatesinvitedUserwith
the created user (id, email address and user type), where the id is the
OWNCLOUD_ID that oCIS uses once the guest is provisioned locally. -
Bugfix - Fix missing labels and low-contrast elements across the web UI: #12526
Several icon-only buttons (search, hide-share, create-user, gallery navigation)
were missing labels, and loading spinners and progress bars did not expose a
name describing what they represent. The global search and create shortcut
dropdowns now use correct roles and states. Tooltips no longer get caught
mid-fade with a low-contrast color when the reduced-motion system setting is
enabled, and low-contrast colors were fixed in the select combobox search input
and in markdown editor links and inline code. -
Bugfix - Fix share metadata corruption during concurrent share operations: #12621
When multiple sharing service replicas processed share operations concurrently
for the same user, the share metadata could become corrupted with references to
missing data, making all shares inaccessible to that user. The received share
cache now uses compare-and-swap (etag) validation to detect concurrent writes
and retries gracefully, preventing metadata corruption. -
Bugfix - Return metadata client init errors from the settings store: #12680
The settings metadata store initialized its metadata client lazily. When
initialization failed, for example because the settings metadata space was owned
by a different user than the configured system user,Store.Init()logged the
error but left the client nil and returned normally. Every subsequent store call
then dereferenced the nil client and panicked with a nil pointer dereference,
which masked the real cause and surfaced as opaque proxy 500s during login.Store.Init()now returns the underlying initialization error and every public
store method short-circuits on it, so callers receive a specific, actionable
error instead of a panic. The client is left nil on failure so the next call
retries initialization. -
Bugfix - Sync the
.psecfile name when a password-protected folder is renamed: #12684Renaming a password-protected folder did not update its
.psecpointer file, so
the main file listing kept showing the old name. This happened both when
renaming the folder via the hidden.PasswordProtectedFolderslocation and when
renaming it from inside the folder-view modal.Renaming the real folder now also renames its
.pseccounterpart. Inside the
folder-view modal, the framed public-link session notifies the parent window at
the moment of rename, so the pointer file stays in sync even on refresh or
another device. -
Bugfix - Reject space images which are too large to be rendered: #12701
Setting a space image larger than the thumbnails service accepts appeared to
succeed but never changed the space image. Uploading the file and assigning it
as the space image are two separate requests, and both completed successfully,
so clients reported success. Only a later preview request, which the assigning
client never observes, was rejected because the image exceeded
THUMBNAILS_MAX_INPUT_IMAGE_FILE_SIZE. As space images are rendered exclusively
as thumbnails, the image was not merely degraded, it was invisible with no error
anywhere in the UI.The graph service now checks the file size when a space image is assigned and
rejects the request with413 Request Entity Too Largeinstead of storing a
reference which cannot be displayed. The previous space image is left untouched.
The limit is read from the newGRAPH_MAX_IMAGE_FILE_SIZEsetting, which
defaults to50MBand must be less than or equal to
THUMBNAILS_MAX_INPUT_IMAGE_FILE_SIZE. Space descriptions (readme) are not
affected. -
Bugfix - Allow space managers to remove shares created by other users: #12705
Space managers with permission to manage a resource's shares were unable to
remove shares that other users had created on that resource. Attempting to
remove such a share failed with a generic server error instead of succeeding.Space managers can now remove any share on a resource within their space,
regardless of who created it, as long as they hold the required permission on
that resource. -
Bugfix - Release the quota of upload sessions with unreadable node metadata: #12739
When an upload's target node lost its metadata, e.g. because an ancestor was
moved to the trash while the upload was still in flight, the upload could never
finish processing. It stayed in "Processing" forever, could not be downloaded or
deleted, and kept consuming the space quota.Cleaning such a session up with
ocis storage-users uploads sessions --clean
did not help either: it removed the uploaded bytes and the session info file
before failing to revert the node, so it destroyed the only copy of the data
without releasing any quota.Cleanup now reverts the node before removing anything irreversible and falls
back to the session metadata when the node cannot be read, so the quota is
released and the orphaned node is removed. If the quota cannot be released the
upload is kept so it can be retried instead of being lost.A new
--orphanedfilter lists the affected sessions:ocis storage-users uploads sessions --orphaned ocis storage-users uploads sessions --orphaned --cleanNote that evaluating the filter reads the node metadata of every session, so it
is only done when the flag is set. -
Bugfix - Open files whose name contains a hash or question mark: #12740
Cmd+Clicking or middle-clicking a file with a
#or?in its name opened the
space root instead of the file, and the top bar showed the space name rather
than the file name. The file's path is carried in a route parameter which the
router percent-encodes when it builds the URL, but the editor route was resolved
twice and resolving twice does not encode twice: the second pass rebuilt the URL
from the still-decoded parameter with the encoding step skipped. The browser
then read everything from the#onward as a fragment, discarding the query
string along with thefileIdneeded to identify the file. Left clicks were
unaffected because they never leave the app.Editor routes are now handed to links unresolved, so the file name is encoded
exactly once and survives both a new tab and an in-app navigation. Hash and
question mark remain valid characters in file names. -
Bugfix - Truncate long resource names instead of overlapping the next column: #12754
In resource tables, a name that was too long for its column was not truncated.
Instead it kept its full width and was painted over the value of the adjacent
column, making both unreadable. This was most visible in the Spaces overview,
where a long space name overlapped the "Manager" column, but it affected every
resource table using the name column, including the files list and search
results, as well as the parent folder path shown below a search result.The name is now truncated with an ellipsis at the column boundary, and the
rename button stays inside the name column. The full name remains available via
the title tooltip on hover. -
Bugfix - Fix uploads stuck in processing with the s3ng storage driver: #12756
Uploads to a
s3ngbacked storage-users service never left the processing
state, so the file stayed unreadable and unmodifiable forever. Every client was
affected equally, because the defect sits below the protocol layer: WebDAV, the
desktop sync client and the Web UI alike.Decomposedfs ignores any event whose storage id does not match its configured
mount id. Thes3ngdriver never received amount_id, so that comparison ran
against an empty string and everyPostprocessingFinishedevent was discarded.
Thes3ngdriver now passesmount_idthe same way theocisdriver already
does.The same key is also added to
OcisNoEventsandS3NGNoEvents. Those build the
storage provider rather than the data provider and configure no events, so today
the value is unused there. Setting it keeps both constructions of the same
storage consistent about their own identity, rather than leaving one of them to
report an empty mount id to any future reader of that option. -
Bugfix - Generate web timestamp by env/git log; make it buildable without .git: #12758
Change compilationTimeStamp to distTimeStamp, set its value from env
SOURCE_DATE_EPOCH, or timestamp of last git commit, or fallback to current time.
Also fixes a problem that raises an error during make ci-node-generate due to
running git clean -xfd in a non-repository directory (usually an extracted
source tarball), showing a message instead. -
Bugfix - Restarting the proxy service on error was causing panics: #12769
Starting oCIS with the
ocis servercommand causes oCIS to monitor the services
being started. When a service fails to start, this monitor tries to restart the
services. For the cause of the proxy service, restarting it was a panic.Now, the proxy service can be restarted as expected, without that panic. Note
that the service might still fail to start if the actual cause isn't fixed, such
as the service's port being taken by a different application. -
Bugfix - Ignore write error after successful read: #12772
In the settings service, we're caching data in the NATSjs store. When reading
service information, that information is written in the cache. Previously,
failing to write that information in the cache caused an error, despite correct
information being retrieved from the service successfully. Now, if the
information isn't written in the cache, we log the failure, but return the read
information without error. -
Bugfix - Use light logo in light mode (with dark blue topbar): #12782
The light theme actually have a dark blue topbar and login screen, where the
dark logo is applied and can hardly be seen. This patch changes it to logo.svg
(the light logo). -
Bugfix - Renaming a resource to its current name is a silent no-op: #12784
Renaming a file or folder to the name it already has failed with a confusing
403 Forbiddenor404 Not Found, and409 Conflictwhen the request
addressed the resource by its id. Every client had to work around it on its own.
AMOVEwhose source and destination resolve to the same resource is now
detected server side and answered with204 No Contentwithout touching the
resource, so the behaviour is consistent for all clients and for both dav
routes. The no-op still requires the move permission: a user who may not rename
the resource keeps getting403 Forbidden. -
Bugfix - Support Collabora Online 26.x in the ocis_full deployment example: #12794
Collabora/code 26.x ships without a shell and without the
coolconfighelper
the ocis_full example relied on to start the container and generate its WOPI
proof key, so the example failed to start and, once running, would reject every
document open with a 500. The example now uses the image's default entrypoint
and a one-shot init container that generates and persists the WOPI proof key
before Collabora starts. -
Bugfix - Fix shift-click range selection in the files list: #12804
We have fixed an issue where shift-click did not select resources between the
anchor and the clicked one, and ignored ctrl/cmd. It now selects the full range,
replacing the current selection unless ctrl/cmd is held, and no longer
highlights the text of the affected rows. Checkboxes now also keep their checked
state in sync with the selection when a click does not change it. -
Bugfix - Search for usernames if memberUid is used for group membership: #12814
Ldap group membership usually use "member" or "uniqueMember" for groups, which
contains a DN as a value. For the case of "memberUid", the value isn't a DN but
just a username / uid. As such, getting the members of a group didn't work
because we expected the values to be DNs.Using "memberUid" as group membership attribute is now supported, and it will
show the group members as expected. -
Bugfix - Truncate long user names in the admin settings users list: #12816
In the admin settings users list, a long user name or display name would
overflow its table column, pushing the columns after it, including the action
buttons, out of place or off screen.Long values in the user name and display name columns are now truncated with an
ellipsis so the table layout stays intact regardless of value length. -
Bugfix - Stop logging every service re-registration: #12833
Services that publish themselves to the service registry re-register on a timer
to keep their TTL alive. Every one of those refreshes wrote a debug line
carrying the whole service record, so an idle deployment running at debug level
produced a steady stream of log entries with no user interaction at all. The
refresh is now silent unless it fails, which is the case that was worth a log. -
Bugfix - Password protection is enforced in the "Shared via link" list: #12835
Creating a password-protected folder also creates a hidden folder which holds
the actual content and carries the password-protected link. That hidden folder
is listed under Shares / Shared via link, but its entry pointed straight at the
content in the owner's personal space instead of at the link. Anyone looking at
that list could therefore open the folder without being asked for the password.The entry now opens the password-protected link, so the password is requested
just like it is when opening the folder from the regular file list. If the link
cannot be determined, the entry is no longer clickable at all. -
Bugfix - Wrap long values in share and user details views: #12840
In the "Access details" popup of a share, and in the admin settings user details
panel, a long user name, display name, email or domain would overflow the popup
or sidebar instead of wrapping, hiding parts of the value and breaking the
layout.Long values are now wrapped onto multiple lines so these views stay within their
bounds regardless of value length. -
Bugfix - Tell public link visitors the link is temporarily blocked: #12841
After a handful of wrong password entries, the brute-force protection
temporarily blocks a password-protected public link. Visitors opening the link
were told "The resource could not be located, it may not exist anymore." or
simply "Unknown error" - including visitors, and owners, typing the correct
password, because the block is checked before the password is looked at. Both
messages were false, and they led link owners to delete and recreate links that
were never broken, forcing them to redistribute the URL.The resolve page now says "Too many failed password attempts for this link. It
has been temporarily blocked, please try again later." both when landing on a
blocked link and when submitting a password to one. No password field is
offered, because a further wrong password is still counted and pushes the
unblock time out.Unrelated failures on that page no longer claim the resource is gone either:
they show the message the server sent, or a neutral "An unexpected error
occurred, please try again later." when it sent none. The not-found wording is
now reserved for an actual not-found. -
Bugfix - Hide app menu items from anonymous public link visitors: #12842
The app drawer in the top bar offered "Activities" and "Library" to anonymous
visitors following a public link. Both apps registered their app menu item
unconditionally at bootstrap, before any authentication context exists, and the
extension registry is shared between the authenticated and the public link
context. Because the public link file view renders the full application layout,
the top bar and its app drawer came along with it - even though the sibling top
bar elements (notification bell, sidebar toggle, home link) already gate
themselves on the authentication context.Following the leaked entries did not expose any data: both apps route with
authContext: 'user', so the visitor was redirected to the login page. What
leaked was the fact that these apps are enabled on the instance.Both apps now contribute their menu item only when a user is signed in, matching
what the files, text editor, app store, admin settings and ScienceMesh apps
already do. With no menu items left to show, the existing top bar condition
hides the app drawer on public links by itself. -
Bugfix - Admin-uploaded logo now overrides theme-specific logos: #12847
Previously, a theme's own per-variant logo defined under
clients.web.themes[].logowould keep showing even after an admin uploaded a
custom logo via the admin settings web app, because the upload only patched the
clients.web.defaults.logokeys. This affected the built-in "owncloud" theme
too, since most of its variants (dark, high contrast, ...) already define their
own logo. The admin-uploaded logo now always overrides a theme's own per-variant
logo. -
Bugfix - Recover the login page after the current user was deleted: #12851
When a user account was deleted while its session was still stored in the
browser, opening the web interface redirected to an authentication error page
and looped there. The identity provider kept accepting the stale logon session
but could no longer resolve the deleted user, so the sign-in flow ended up
re-issuing the authorization request without its parameters and the browser was
sent back to the same error over and over. The only way out was to clear the
browser data manually before a different user could sign in.The identity provider now detects this stuck authorization loop, expires the
stale logon session on the server side and restarts a clean login, so the
sign-in form is shown again and a different user can sign in right away. -
Bugfix - Apply renewed access token in embed mode with delegated authentication: #12856
In embed mode with delegated authentication the host application renews the
access token by posting an "owncloud-embed:update-token" message into the
iframe. The message listener was registered as an unbound method reference, so
it crashed on every incoming message before the renewed token could be applied.
It also passed the whole message payload to the user context update instead of
the access token string. The embedded Web instance therefore kept using the
initial access token until it expired and the user got logged out, even though
the host had delivered fresh tokens in time. -
Bugfix - Resolve Safe/Vault permalinks: #12881
A permanent link to a file inside the Safe failed for the recipient. Such links
now open the shared file. -
Bugfix - Deny Safe/Vault access to users without permission: #12884
Users whose role did not grant Safe access could still reach it by editing the
URL. Such users are now denied and shown the access-denied page. -
Bugfix - Cache LDAP instance mapper lookups: #12899
In multi-instance deployments, resolving a user's instance name/ID during
GET /graph/v1.0/users(and group member expansion) issued a fresh, uncached LDAP
search per instance/guest attribute value on every request. Under load this
multiplied into large numbers of redundant LDAP round-trips per page of users,
saturating the LDAP connection pool and causing request timeouts. The LDAP
identity backend now caches instance mapper lookups, including negative
(not-found) results, for a configurable TTL
(OCIS_LDAP_INSTANCE_MAPPER_CACHE_TTL, default 60s). -
Bugfix - Do not share vault resources with users who cannot access them: #12905
A vault ("Safe") resource could be shared with a user lacking the "Vault mode"
permission. Such a user can never enter the vault, so the share was useless to
them, while its name was still disclosed to them.Sharing a vault resource now requires the grantee to hold that permission, and
the check fails closed. The recipient picker no longer offers ineligible users,
nor groups at all, since the permission is assigned per account. -
Bugfix - Explain why an upload or a duplicate does not fit the space quota: #12943
An upload rejected for lack of room named only the shortfall ("You need
additional 1 MB"), and a failed duplicate was reported as a failed move with
"Insufficient quota" underneath. Both messages now name the space and what to do
about it, and a failed duplicate is reported as one.The upload check also measured only the last file of a batch, and skipped the
check altogether for a space with nothing left, because a remaining quota of 0
was read as "unknown". -
Bugfix - Correct introduction version for OCIS_LDAP_INSTANCE_MAPPER_CACHE_TTL: #12948
We changed the documented introduction version of the
OCIS_LDAP_INSTANCE_MAPPER_CACHE_TTL from 8.0.0 to 8.3.0. -
Bugfix - Text and BMP file previews failed where libvips has no ImageMagick: #12961
Downloading the preview of a text or BMP file failed with a
500 could not get thumbnailerror on systems where libvips comes without ImageMagick support,
such as minimal container images. The rendered text image was passed through a
BMP encoding round-trip first, and uploaded BMP files were handed to libvips as
bytes; libvips can only load BMP images via ImageMagick.The rendered text image is now handed over to libvips directly from memory, and
BMP files are decoded in Go before the handover, so both no longer depend on
ImageMagick being installed alongside libvips. -
Bugfix - Unify when the maintenance banner clears: #12966
The Web frontend showed the maintenance banner inconsistently depending on which
HTTP client happened to make the last request: the webdav client cleared the
banner on any error that was not a maintenance response, including a plain 404
or 500, while the other client only cleared it on a genuine successful response.
Whether the banner disappeared during real maintenance could therefore depend on
which request happened to run last.Both clients now agree: the maintenance banner is only raised by the explicit
maintenance response, and any other real response from the server clears it,
since that is not the same as general unhealthiness. Only a transport-level
failure, where no response is received at all, leaves the banner state
untouched. -
Bugfix - Restoring an already-restored trash item now returns 404: #12969
Issuing a second restore request for a trash item that had already been restored
or purged returned a 500 (internal server error) instead of a 404 (not found).
This made benign duplicate restores, such as those caused by a sync client
retrying a request, look like server errors. The restore operation now reports
404 for this case, matching the existing behavior of purging an already-purged
item. -
Bugfix - Do not allow credentials for wildcard CORS origins: #12983
CORS responses no longer send
Access-Control-Allow-Credentials: truewhen the
configured origins permit any origin: an empty list,*, or a wildcard pattern
such ashttps://*. In those cases credentials are dropped and a warning is
logged. This applies across all CORS paths (the shared HTTP middleware, the reva
interceptor used by the frontend and ocm services, ocdav, and the tus upload
handler). Explicitly configured origins are unaffected and keep credentials, so
intended cross-origin setups continue to work. -
Bugfix - Stop endless redirect loop when vault MFA step-up fails: #12985
Web requested the vault MFA level via
acr_values, which is a voluntary claim.
IdPs like Keycloak return a token with a loweracrinstead of an error when
the user can't complete the second factor (none enrolled, device not at hand).
Web then started the step-up again on every return, trapping the user in a
redirect loop. The step-up request now carries the vault page as OIDC state. If
the IdP answers it without the requiredacr, web stops retrying, reloads the
page outside the vault and shows an error message there. Leaving the vault needs
a full page load, because vault mode is fixed for the lifetime of the page.
Returning without the IdP answering, e.g. via the browser's back button, still
starts a new step-up. -
Bugfix - Fixed low color contrast on disabled danger buttons: #12992
Disabled buttons using the "danger" styling, such as the "Empty trash bin"
button when there is nothing to delete, showed their label text with very low
contrast against the button background, making the text hard to read.The muted background color used for these buttons in a disabled state has been
darkened, and the fading effect applied to disabled buttons no longer washes out
the danger button background, restoring readable contrast between the label and
the background. -
Bugfix - Fixed low color contrast on nav and primary button hover states: #12993
Non-active sidebar navigation items, as well as buttons using the "primary"
styling, showed their text and icons in black on top of a dark hover background
in some themes, making them hard to read while hovering.The hover state for these elements now switches to a light color instead of
always using black, restoring readable contrast between the text and the
background while hovering. -
Bugfix - Fixed low color contrast on dropdown menu item hover text: #12994
Items in dropdown menus, such as the "New" file/folder menu, changed their text
to a color meant for use as a background rather than as text when hovered. On
top of the generic hover background used across the app, this produced poor
contrast in some themes.Hovered menu items now keep the same text color already used before hovering,
which reads correctly against the hover background in every theme. -
Bugfix - Fixed low color contrast on share permission dropdown hover text: #12995
The share permission dropdown's role options, such as "Can view" or "Can edit",
showed their hovered text in a color too close in lightness to the hover
background in the dark theme, making it hard to read.The hover text color has been lightened slightly, restoring readable contrast
between the text and the background while hovering. -
Bugfix - Fixed low color contrast on file name in editor topbar: #12997
The file name and extension shown in the topbar when a file is open, for example
in an editor, were displayed in white on top of a light brand-colored background
in some theme variants, making the text hard to read.The text now uses a dark color instead, restoring readable contrast against that
background. -
Bugfix - Fixed low color contrast on disabled danger button text: #12998
Disabled filled danger buttons, such as the "Empty trash bin" button in the
deleted files view, displayed their text and icon in a color too close to the
background fill, making them hard to read.The disabled text and icon color is now forced to white, restoring readable
contrast against the button's background. The vault light theme's muted danger
color was also darkened, since it was too light to meet contrast requirements
against white text. -
Bugfix - Return a retryable 503 when the OIDC userinfo call fails transiently: #12999
A transient failure of the OIDC userinfo call (a timeout, a network error or a
5xx/429 from the IdP) was mapped to HTTP 401. Clients read the 401 as an invalid
session and logged the user out on a brief IdP slowdown.The proxy now distinguishes a transient IdP failure from an authentication
failure and returns a retryable 503 (with Retry-After) for the former, so
clients retry and keep their session. A genuinely invalid or expired token still
returns 401. -
Bugfix - Fixed low color contrast on notification bell badge: #13000
The unread notification count badge on the notification bell used a hardcoded
red background with white text, which fell below the WCAG AA contrast
requirement for text that size.The badge now uses the design system's danger color tokens instead, which are
already tuned to keep sufficient contrast with their paired text color across
all theme variants. -
Bugfix - Open Safe permanent links from outside the Safe: #13001
A permanent link to a file in the Safe, opened in a regular Drive tab, showed
"An error occurred while resolving the private link" instead of the file. The
Web frontend recognized Safe files by a storage provider id that the server only
sends to sessions already inside the Safe, so a Drive tab never redirected the
link into the Safe.The Safe storage provider id is fixed, so the frontend now uses it as a
constant, like the share jail and OCM ids. This also keeps Safe notifications
out of the Drive view and lets the invite form recognize Safe resources in Drive
mode. ThevaultStorageProvidergetter of the web-pkg capability store is
removed; useVAULT_STORAGE_PROVIDER_IDfrom web-client instead. -
Bugfix - Fixed arrow-key navigation in the notification dropdown: #13002
Opening the notification bell's dropdown did not move keyboard focus into it.
Arrow-key navigation only started working after an extra, unrelated Tab press,
and pressing an arrow key too early scrolled the page instead, which looked like
the dropdown had closed.The dropdown now moves focus to its first item as soon as it opens, so arrow
keys work immediately, matching the behavior of other click-triggered dropdowns
in the application. -
Bugfix - Notification bell now announces the unread count: #13003
The notification bell's accessible name was a static "Notifications" string
regardless of how many unread notifications there were. Since that label
overrides all other content for assistive technology, screen reader users never
heard the unread count that sighted users see on the bell's badge.The bell's accessible name and tooltip now include the exact unread count, with
correct singular/plural wording. -
Bugfix - Added a keyboard shortcut to move focus out of the text editor: #13004
Opening the text/markdown editor moved keyboard focus straight into the edit
area, but Tab is bound to indenting rather than moving focus, so there was no
reliable way to reach the toolbar without leaving the file entirely. The
editor's own built-in escape hatch for this doesn't work on a standard Mac
keyboard, since the key combo it relies on is consumed by macOS as a diacritic
shortcut before it reaches the page.Pressing Ctrl+M now moves focus from the edit area to the toolbar, the same way
on every platform. The editor's accessible description also announces this
shortcut for assistive technology users. -
Bugfix - Hide "Shared via link" when public sharing is disabled: #13005
The Shares navigation (the desktop tab list and the mobile drop-down) always
offered a "Shared via link" entry, even when public link sharing was disabled
for the account — for example in the Vault, where the backend rejects public
link creation and the capabilityfiles_sharing.public.enabledreported
false. The entry led to a page that could never contain anything.The Shares navigation was changed to hide the "Shared via link" entry whenever
files_sharing.public.enabledisfalse. Anyone who still reached the via-link
route directly, including through the legacy/list/shared-via-linkredirect,
was redirected to "Shared with me" at navigation time, keeping the current route
scope (e.g.vault) intact. When public sharing was enabled, all three Shares
navigation entries continued to behave exactly as before. -
Bugfix - Fixed missing accessible name on button loading spinner: #13018
OcButton's loading spinner is arole="img"element, but it had no accessible
name. This tripped an axerole-img-altviolation on any page whose e2e a11y
check ran while a button was in its loading state, such as the public link
password page's "Continue" button.The spinner now gets a real accessible name ("Loading") via
OcSpinner's
ariaLabelprop, markedaria-live="polite"so it is actively announced to
screen reader users instead of only being described if focus happens to already
be on the button. -
Bugfix - Announce status messages to screen readers: #13024
Status messages such as "copied to clipboard" or "file restored successfully"
were not reliably read out by screen readers. The underlying announcement area
was never cleared between messages, so a repeated or rapid message could be
silently dropped, especially when combined with a focus change elsewhere on the
page.The announcement area is now cleared before each new message and refilled after
a short delay, so status messages are announced consistently. -
Bugfix - Keep keyboard focus on the trigger when a dropdown closes: #13025
Dropdown and context menus that close on item click (e.g. the per-file "..."
menu) removed the clicked item from the page as they closed, so keyboard focus
fell back to the page body. Screen readers then re-announced the whole page,
drowning out any status message the action had just triggered.The dropdown now returns focus to the button that opened it when it closes,
unless the clicked action already moved focus somewhere else on its own. -
Bugfix - Announce autocomplete comboboxes correctly to screen readers: #13041
Autocomplete fields such as the language and design selectors on the account
page did not announce themselves as comboboxes to assistive technology. The
combobox role and its related ARIA attributes were set on a wrapper element that
could not receive keyboard focus, while the actual focusable input exposed a
generic, hardcoded label instead of the field's own label.The combobox role, its state attributes and the accessible name are now set
directly on the focusable input, so screen readers announce the field as a
combobox with the correct label. -
Bugfix - Restore focus after changing the account language: #13045
Selecting a new language in the account page's Language dropdown dropped
keyboard focus to the page body instead of keeping it on the dropdown, and the
confirmation message was not announced to screen readers afterward.The language change triggers a fair amount of background work (reloading
translations, switching the active language, saving the preference) before it
finishes, which raced against the dropdown's own best-effort focus handling.
Focus is now explicitly restored only once that work has fully settled, and
before the confirmation message is shown, so the announcement is no longer
cancelled by a focus change happening right after it. -
Bugfix - Stop endless redirect loop when admin settings MFA step-up fails: #13069
The admin settings route guards required MFA via
requireAcr(), which
redirected to the IdP whenever the token'sacrdid not match. IdPs like
Keycloak answer anacr_valuesrequest they can't satisfy with a loweracr
instead of an error, so a user without a second factor at hand was trapped in a
redirect loop.requireAcr()now uses the same protection as the vault: the
step-up carries its target as OIDC state, and if the IdP answers it without the
requiredacr,requireAcr()returns false. The admin settings then redirect
to the default view and show an error message. -
Bugfix - Fix file and folder downloads in vault mode: #13097
Downloading a file in the vault failed with a 403 error. A download uses a
signed link without a login token. Thus the proxy uses the stored MFA status of
the user. The proxy did not store this status. Now the proxy stores it after it
knows the user. A download is accepted if the user had a request with MFA within
the MFA session duration.Downloading a folder or several files in the vault failed with a 404 error. In
vault mode, the web UI requested the signing key from a wrong address. Now the
web UI uses the correct address. -
Bugfix - Fix the LDAP master-ID filter when the base filter is empty: #13100
The function
EnhanceFilterWithMasterIDinocis-pkg/ldap/filter.goadds a
master-ID clause to an LDAP filter with OR. An empty filter means "no
restriction". Before this fix, the function replaced an empty filter with a
master-ID-only filter. This action restricted an unrestricted search to
master-ID users only.The bug broke the search for a user on another instance in multi-instance
deployments. This search uses the Graph API endpoint/graph/v1.0/users.
Multi-instance deployments use this search to find a user to share a resource
with.Now the function keeps an empty filter unchanged. The function still adds a
master-ID clause to a filter that is not empty.The
graph,auth-basic,users, andgroupsservices also use this function
to compute their default LDAP user filter whenOCIS_MULTI_INSTANCE_MASTER_ID
is set. An empty user filter now means these services resolve or authenticate
every user in the shared LDAP directory, not only master-ID users. Each of these
services now rejects startup whenOCIS_MULTI_INSTANCE_MASTER_IDis set and its
own user filter is empty. Set an explicitOCIS_LDAP_USER_FILTERfor every
multi-instance deployment. -
Bugfix - Stop logging "no user in context" for data gateway requests: #13101
The proxy's create-home middleware logged an error for every request that
carried a reva token but no user. reva's internal downloads through the data
gateway (/data) are such requests, so every file download added an error-level
line. These requests are now passed on with a debug-level log. -
Bugfix - Show an error instead of "no deleted files" for inaccessible trash: #13105
Members of a space who are not allowed to list its trash, for example members
with the "Can edit" role, were told that the space has no deleted files, even
though files had been deleted. The trash view now tells the user that the
deleted files could not be loaded and that they might lack the permission to
view them. A trash that is really empty still shows the "no deleted files"
message. -
Bugfix - Fix AuthApp and basic auth requests with custom PROXY_USER_OIDC_CLAIM: #13107
We fixed AuthApp (app password) and HTTP basic auth requests returning an
internal server error whenever PROXY_USER_OIDC_CLAIM was set to anything other
than its default value. Both authenticators put the already authenticated user
directly into the request context instead of faking incomplete claims for the
account resolver to re-resolve. We also made sure a user who only ever
authenticates this way still gets a default role assigned, and that these
requests keep getting rejected on deployments with multiple instances enabled,
since neither carries tenant-membership information. -
Change - Respect proxy environment variables for OIDC requests: #12703
The proxy and webfinger services now route OIDC requests through the
HTTP_PROXYandHTTPS_PROXYsettings from the environment. Deployments that
should not send the OIDC issuer host through the proxy, or whose proxy cannot
reach that host, must list the issuer hostname inNO_PROXY, otherwise
authentication can fail when oCIS's own external hostname is reached through the
proxy. -
Change - Replace axios with the native fetch API in Web: #12910
The Web frontend no longer depends on axios. All HTTP traffic goes through a
single fetch-based client, and the libre-graph client is generated from the
typescript-fetchtemplate instead oftypescript-axios.Sending requests is a drop-in change.
HttpClientkeeps its per-request config
includingdata, keepscancel(), still resolves a non-JSON body as text, and
still exposes response headers asheaders['etag']as well as
headers.get('etag'). Errors still carry the body and status aserror.data/
error.statusCodeand aserror.response.data/error.response.status.
mockAxiosResolveandmockAxiosRejectstill work, deprecated in favour of
mockHttpResponseandmockHttpError.Per-request
headersare merged over the client-wide ones case-insensitively,
so an override replaces the header it names whatever case either side used.Maintenance mode is now also detected on
clientService.httpAuthenticated.
Before, only the unauthenticated, graph and ocs clients watched responses for
it, as the authenticated client had no response interceptor. Requests through it
now raise and clear the maintenance flag like any other, and they update
lastSuccessfulRequestTime, which seeds the MFA expiry timer.Code that touches axios directly has to be adapted:
new HttpClient()takes{ baseUrl, staticHeaders, headers, onResponse }
instead of{ config, requestInterceptor, responseInterceptor }. Clients from
ClientServiceare unaffected. - The per-request config dropstimeout,
withCredentials,onUploadProgress,cancelToken,paramsSerializer,
transformRequest/transformResponse,validateStatusandbaseURL;
responseTypedropsdocumentandstream. - The per-requestheadersare
typed asHeadersInit, so aHeadersis accepted as well as a plain object.
Assigning into them after the fact (config.headers.Authorization = …) no
longer type-checks; build the object first, or usenew Headers()andset().error.responsecarries the body onerror.response.data, as it did with
axios. Its underlying stream is consumed, soerror.response.json()is not
available. -graph(),ocs(),UrlSignandWebDavOptionstake a
FetchClient, and the latter two renameaxiosClienttohttpClient.
webdav()is unchanged. - Graph fields with an OData annotation use their
generated camelCase names, e.g.atLibreGraphPermissionsActions. The wire
format is unchanged. - Graph responses are rebuilt from the fields the spec
declares, which is what makes the renaming above possible. A field the spec does
not declare is dropped, so the oCIS-onlyattributeson users is added to the
spec before generating. A declared field the server omits is present and holds
undefined, so'accountEnabled' in userno longer tells whether the server
sent it. Compare againstundefinedinstead. -
CollaboratorAutoCompleteItem.attributesis optional, matching theattributes
on the generatedUser. The field is only there when
OCIS_USER_SEARCH_DISPLAYED_ATTRIBUTESis configured, so read it as
item.attributes?.join(…). - The generated client loses its*ApiFactory,
*ApiFpand*AxiosParamCreatorexports. The*Apiclasses now take one
options object per operation and resolve with the payload. -
@ownclouders/web-test-helpersno longer has amocks/axiosmodule path.
-
Change - Replace GRPC_MAX_CONNECTION_AGE with client keepalive: #13020
The grpc clients now send a keepalive ping while a request is in flight and fail
the requests on a connection whose peer stops answering, instead of waiting for
as long as the caller allows. This covers both the reva CS3 clients (gateway,
storage-users, storage-shares, ...) and the go-micro based clients used for
inter-service calls between the other oCIS services. Set
GRPC_CLIENT_KEEPALIVE_TIME and GRPC_CLIENT_KEEPALIVE_TIMEOUT to enable and tune
this; leave them unset to keep grpc's own default (no pings).GRPC_MAX_CONNECTION_AGE has been removed. It only closed healthy connections on
a timer, never ended a request that was already in flight, and silently did
nothing when its value had no unit suffix. -
Change - Remove the MFA session extension popup in vault mode: #13085
In vault mode, the web UI showed a popup shortly before the multi-factor
authentication session was about to expire, offering to extend or dismiss it.
Extending only reset a timer in the browser and did not renew anything on the
server, so the popup has been removed.The frontend service no longer exposes the MFA session duration in its
capabilities, and itssession_durationsetting has been removed. The
OCIS_MFA_SESSION_DURATIONenvironment variable is still used by the proxy
service. -
Enhancement - Bump Reva version: #12051
Bumped reva version
#12051
#12087
#12137
#12302
#12439
#12266
#12730
#13066
#13081 -
Enhancement - Ship ownCloud branding as the default login background: #12406
The builtin IDP login page now ships the ownCloud branding image as its default
background. The bundled image (services/idp/assets/identifier/static/media,
referenced from theme.css) is anchored to the top right so the ownCloud logo
stays fully visible at every viewport size instead of being cropped. Operators
can still point the login background at a different image via
IDP_LOGIN_BACKGROUND_URL.The same branding background is also embedded in the web service theme assets
(services/web/assets/themes/owncloud/assets/loginBackground.jpg), so the
ownCloud Web login page shows it out of the box, taking precedence over the
background bundled with the vendored web release.Additionally the ocis_keycloak deployment example now ships a custom Keycloak
login theme ("owncloud") that applies the same branding background and styles
the login form to match the IDP login screen. -
Enhancement - Apply Kiteworks branding to the web theme: #12464
The default oCIS theme now uses the Kiteworks OSPO name, slogan and logos across
all regular and vault mode themes. -
Enhancement - Configurable Keycloak invitation actions and working ocis_full SMTP: #12467
The invitations service now lets operators configure the Keycloak required
actions that are sent to invited guests via the execute-actions email, using the
newINVITATIONS_KEYCLOAK_EXECUTE_ACTIONSenvironment variable. It defaults to
UPDATE_PASSWORD,VERIFY_EMAIL; configured values are passed to Keycloak as-is,
and the service falls back to the defaults when none are configured, so an
invited guest always has a way to set up their account.The Keycloak realm shipped with the
ocis_fullexample deployment now points
its SMTP server at the bundled mailpit instance. Previously the realm shipped
with an empty SMTP configuration, so Keycloak silently dropped every mail it
tried to send (including the guest invitation email) even though the invitations
service correctly requested it. -
Enhancement - Close Collabora WOPI CheckFileInfo property gaps: #12593
The collaboration service's Collabora CheckFileInfo response was missing several
properties that the Microsoft and OnlyOffice fileinfo types already hadcase
handling for, but that were never populated in the shared properties map:
Version, LastModifiedTime, ReadOnly, SupportsUpdate, IsAnonymousUser, several
file URLs (CloseUrl, DownloadUrl, plus the already-computed HostEditUrl/
HostViewUrl/FileSharingUrl/FileVersionUrl), the BreadcrumbBrandName/
BreadcrumbBrandUrl breadcrumb pair, an EditModePostMessage flag, and two new
Collabora-specific properties, IsUserLocked and IsAdminUser.We've added all of these. Note that since Microsoft and OnlyOffice already had
casehandling for ReadOnly and CloseUrl (and Microsoft for DownloadUrl too),
populating those keys unconditionally changes their CheckFileInfo output as
well, not just Collabora's: ReadOnly now actually surfaces astruefor
read-only/view-only sessions on all three targets, and CloseUrl (plus
DownloadUrl for Microsoft) is now populated where it previously wasn't. Only
IsUserLocked and IsAdminUser are genuinely Collabora-only additions with no
matchingcaseelsewhere. -
Enhancement - Add EPUB library: #12648
The EPUB reader now includes a library for discovering and organizing books
stored across accessible personal and project spaces. The library extracts
metadata and cover images in the browser and supports search, sorting, filters,
favorites, custom shelves, reading statuses, grid and list views, and resuming
from the reader's saved position.Book metadata and covers are cached locally. Library preferences are stored in
the browser and are not synchronized between browsers or devices. -
Enhancement - Add "Undo" action to the delete success notification: #12650
Deleting a file or folder now shows an "Undo" action alongside the "moved to
trash bin" notification, letting users restore the deleted resources directly
from the toast instead of navigating to the trash bin. The action is only shown
when the resources can be resolved in the trash and the space supports restoring
from it. The notification pauses its auto-dismiss timer while hovered or
focused, so it does not disappear before the action can be used. Pressing Ctrl+Z
(or Cmd+Z on macOS) while the notification is visible triggers the same undo. -
Enhancement - Use a more distinctive icon for the software license link: #12669
The "Software License Information" entry in the help menu and apps menu used the
generic "scales" icon, which is easy to confuse with other justice- or
balance-related icons. It now uses the "file-shield" icon, which better conveys
a legal/license document. -
Enhancement - Add Mermaid diagram editor: #12676
Added a dedicated split-pane editor and live preview for standalone Mermaid
diagram files (.mmd/.mermaid). Previously Mermaid rendering only worked
inside a fenced code block of a Markdown document; there was no way to edit a
diagram on its own without wrapping it in Markdown first. -
Enhancement - Restrict personal drive information to the owner and admins: #12742
The
/graph/v1.0/users/{userID}/drive,/graph/v1.0/drives/{driveID}and
/graph/v1.0/drivesendpoints now drop personal spaces the caller does not own
unless the caller holds account management permission, leaving project and other
shared space types unaffected. The single-drive and per-user lookups return the
same404as a missing drive, so the response does not depend on the target
user's existence. -
Enhancement - Add a command to recalculate the treesize of a space: #12746
The reported quota usage of a space can drift from the data actually stored on
disk. The treesize of a directory is maintained as a running counter that is
updated on every change, so a failed or incomplete update leaves the counter
wrong. Removing a node without propagating the size change, for example, leaves
its size counted against the quota forever, with no way to reclaim it.The new command walks a space bottom up, recalculates the treesize of every
directory from the actual size of its children and corrects the stored values:ocis storage-users spaces recalculate-treesize --space-id <id> ocis storage-users spaces recalculate-treesize --space-id <id> --dry-run=falseOmit
--space-idto process all spaces. As with the other maintenance commands,
--dry-rundefaults to true, so the command reports what it would change until
it is explicitly told to write. -
Enhancement - Add TLS support for NATS store and registry connections: #12765
All
nats-js-kvstore, cache, and service registry connections now support TLS.
Configure viaOCIS_CACHE_ENABLE_TLS,OCIS_PERSISTENT_STORE_ENABLE_TLS, and
MICRO_REGISTRY_ENABLE_TLS, with corresponding*_TLS_INSECUREand
*_TLS_ROOT_CA_CERTIFICATEvariants per connection type. -
Enhancement - Update app store repository: #12793
We've updated the default app store repository to use the new ownCloud
Marketplace instead of the awesome-ocis repository. The default
Content-Security-Policy configuration was also updated to allow connections to
the new marketplace domain. -
Enhancement - Colour tag chips by tag name: #12892
Tag chips were all the same grey, so a file's tags were hard to tell apart at a
glance and the same tag looked different to nothing across the app.Tag chips are now filled with a colour derived from the tag name, so a given tag
always looks the same — for every user, on every device, without the colour
being stored anywhere. Themes supply the palette through a new
designTokens.tagColorsList, and the label colour is chosen per fill so it
stays legible in both the light and dark themes.The tag overflow indicator on the files list also became a disclosure button
that shows the hidden tags in a popover instead of opening the sidebar. It opens
on click or on Enter/Space, closes on Escape, and reports its state to assistive
technology. -
Enhancement - Add TLS support for the frontend stat cache store connection: #12931
The frontend service was the only remaining place where a
nats-js-kvstore
connection could not be secured. Its OCS stat cache forwarded the store type,
nodes, database, table, TTL and credentials to reva, but not the TLS settings,
so the connection stayed plaintext with no operator toggle to change it. The
stat cache now honoursOCIS_CACHE_ENABLE_TLS,OCIS_CACHE_TLS_INSECUREand
OCIS_CACHE_TLS_ROOT_CA_CERTIFICATElike every other cache and store. -
Enhancement - Clarify the NATS store TLS insecure options: #12941
The descriptions of the
*_TLS_INSECUREoptions for thenats-js-kvstore,
cache and service registry now state that they disable authentication of the
NATS server and are for testing only. -
Enhancement - Inline images in the markdown editor: #12967
Uploading an image in the markdown editor did nothing at all - neither
drag-and-drop nor the "Upload Images" toolbar button produced a result, a
progress indicator, or an error. The feature had been deliberately suppressed
because there was no answer to where an uploaded image should be stored, and
because a recipient of a public link to a single markdown file has no permission
to read an image stored next to it.Images dropped or picked in the markdown editor are now encoded into the
document itself as base64 data URIs, so a shared document carries its own images
and needs no further permissions. Because the image bytes are now part of the
document, two limits keep documents small enough to stay fully searchable: a
maximum size per image, and a budget for the total size of all images in one
document. An image that exceeds either limit is rejected with a notification
naming the image and the limit, instead of failing silently.Both limits are configurable through the text editor's app configuration as
maxImageSizeandmaxDocumentImageSize, given in bytes and defaulting to 2 MB
and 10 MB respectively.The editor's "Crop And Upload" entry is no longer offered. Cropping was not part
of the reported problem, so it stays out until users ask for it, and images are
inlined exactly as they were picked. -
Enhancement - Default 30-day expiration for vault shares: #12988
When a user or group share of a vault file or folder is created without an
expiration date, the server now preconfigures a default expiration (30 days by
default, configurable viaGRAPH_DEFAULT_VAULT_SHARE_EXPIRATION_DAYS) to
encourage data minimization. The sharer can override or shorten this value.Non-vault shares and space memberships are exempt and stay unbounded, as space
memberships represent a permanent organizational role. -
Enhancement - Make the public share expiry janitor configurable: #13020
The sharing service runs a background janitor that permanently deletes expired
public shares. Whether that cleanup runs at all could previously only be set in
the sharing service's yaml config, and how often it ran was fixed internally
with no way to tune it.Both settings are now exposed as environment variables:
OCIS_SHARING_ENABLE_EXPIRED_SHARES_CLEANUP toggles the cleanup (default:
enabled, expired shares stay hidden from listings even when disabled), and the
new OCIS_SHARING_JANITOR_RUN_INTERVAL sets the interval in seconds between
janitor runs (default: 3600). -
Enhancement - The public link resolution flag added to PROPFIND: #13020
The public link resolution flag and the context timeout added to PROPFIND
request The ocdav PROPFIND handler resolves public link shares to populate the
oc:share-type property. A new toggle for skipping that lookup. The toggle is now
exposed as OCDAV_DISABLE_PROPFIND_PUBLIC_LINK_RESOLUTION, which can be set to
reduce load on services for large collections. Also, the bounded context was
added for least public share request. Since this property is needed only to
display an icon next to files in the list, indicating that a public link exists,
it can be omitted if the ListPublicShares request is slow. -
Enhancement - Add a --timeout flag to the search index command: #13052
ocis search indexcalled the search service with a fixed 10 minute request
timeout. The service walks the whole space inside that request, so once the
timeout expired the walk was cancelled with "error walking the tree: context
canceled" and everything after that point stayed unindexed. A space whose walk
takes longer than ten minutes, for example because the content extractor is slow
on a few files, could never be fully indexed from the command line.The timeout is now a flag.
--timeouttakes a duration (default10m, so the
behaviour is unchanged out of the box);0waits indefinitely. -
Enhancement - Record tag changes in the audit log: #13054
Adding or removing tags on a file or folder left no trace in the audit log. The
graph service already publishesTagsAddedandTagsRemovedevents for every
change, but only the search service listened to them.The audit service now records both:
file_tags_addandfile_tags_remove
entries carry the acting user, the file id and path, the space owner and the
tags concerned. The graph service also sets the timestamp on the two events,
which it left empty before.