Shinydrive 2.26.5.0 (October 2026)
This release makes the Shinydrive Windows Client more resilient on unstable networks, updates Shinydrive Server to current Tomcat and Java versions, and replaces SOAP with REST for communication with OpenText Content Server.
Released October 20, 2026
This release makes the Shinydrive Windows Client more resilient on unstable networks, updates Shinydrive Server to current Tomcat and Java versions, and replaces SOAP with REST for communication with OpenText Content Server.
[!WARNING] This is a major upgrade. Shinydrive Server no longer uses OpenText Content Web Services (CWS) or Shinydrive Service (sd-csws), it needs Tomcat 10.1 or 11 with Java 21, and it needs the Shinydocs Service module 1.6.23 on Content Server. Read Before you upgrade before you start.
Before you upgrade
Until now, a Shinydrive installation ran three web applications on Tomcat: OpenText Content Web Services (cws), Shinydrive Server (shinydrive-server) and Shinydrive Service (sd-csws), on one Tomcat or on two. From 2.26.5.0, Shinydrive Server talks to Content Server directly through its REST API and the Shinydocs Service module, so it is the only web application Shinydrive needs.
| Component | Before 2.26.5.0 | From 2.26.5.0 |
|---|---|---|
| Application server | Tomcat 9 | Tomcat 10.1 or 11, with Java 21 |
| Web applications on Tomcat | cws, shinydrive-server and sd-csws |
shinydrive-server only |
| On Content Server | An earlier version of the module (ShinyService Content Server Module) | Shinydocs Service module 1.6.23 (required) |
To upgrade:
- Install the Shinydocs Service module 1.6.23 on Content Server. Shinydrive 2.26.5.0 needs this version, so install it at the same time as you upgrade Shinydrive Server.
- Set up Tomcat 10.1 or 11 with Java 21. Tomcat 9 is no longer supported.
- Deploy Shinydrive Server 2.26.5.0 only. Don't deploy
cwsorsd-cswson the new Tomcat. Once Shinydrive is working, you can remove them from your old Tomcat, unless another application uses CWS. - Check each Content Server content source in the Shinydrive administration settings:
- A content source now has one address, the Content Server URL (for example
https://otcs.contoso.local/otcs/llisapi.dll). The separate CWS and Shinydrive Service addresses are no longer used, so there's nothing to re-enter for them. - If users sign in through OTDS (single sign-on, a drive with OTDS authentication, or Authenticate through OTDS), enter the OTDS Authentication URL, for example
https://otds.contoso.local. This field is empty after the upgrade, and OTDS sign-ins fail until it is set. You don't need to enter the OTDS resource ID: Shinydrive reads it from Content Server.
- A content source now has one address, the Content Server URL (for example
What’s New
- Tomcat 10.1 and 11 support. Shinydrive Server now runs on Tomcat 10.1 or Tomcat 11 with Java 21.
- REST integration with Content Server. Shinydrive Server now uses REST instead of SOAP to communicate with OpenText Content Server. Shinydrive Server no longer uses OpenText Content Web Services (CWS) or Shinydrive Service (sd-csws). It needs the Shinydocs Service module 1.6.23 on Content Server.
- Better performance on unstable networks. The Shinydrive Windows Client stays responsive when the network connection is slow or intermittent.
- New Windows Client installer. The Shinydrive Windows Client has a new, improved installer.
- New switches are available for the executable to customize your install:
| Switch | Description |
|---|---|
/quiet |
No UI |
/passive |
Progress only, no prompts |
/norestart |
Never restart. Without it, /quiet and /passive restart automatically when required, which is every install or upgrade |
/log file |
Log file location. Defaults to %TEMP%\Shinydrive_*.log |
/uninstall |
Removes Shinydrive and its optional components. The Dokan driver stays installed |
INSTALLOFFICEADDIN=1 |
Also installs the Office add-in (Word, Excel, PowerPoint and Visio) |
INSTALLOUTLOOKADDIN=1 |
Also installs the Outlook add-in |
INSTALLAPPFINDER=1 |
Also installs AppFinder, for Content Server documents that have no file extension |
Fixes
- Shinydrive no longer crashes or makes Windows unresponsive when Content Server can’t be reached.
- Files in the mounted drive can now be deleted as expected.
- Fixed a missing license error that could appear the first time Shinydrive starts.
- Licenses without an end date are now supported.
Requirements
| Component | Version |
|---|---|
| Application server | Tomcat 10.1 or 11 |
| Java | 21 |
| OpenText Content Server | 22 or later |
| Shinydocs Service module (on Content Server) | 1.6.23 |