Excellent suggestion @miked
I’ll get this added to our backlog for sure.
Forum wide moderators
Excellent suggestion @miked
I’ll get this added to our backlog for sure.
Hey there @ataricze
We’re anticipating Q4CY26 for this capability. Happy to arrange a roadmap discussion if you want to send me a DM here or an email?
Many thanks
@Bolder You are correct, manual update states incorrect details that are miss leading. I’ve updated the docs and they should be published shortly to now properly reflect the manual update and also the offline update process.
For those behind Proxy, you can follow the https://docs.multiportal.io/kb/article/0000050/.
Just a heads up, at this stage if you have used the offline-update, there is no method currently to update the installation via the automatic process.
Woody
Hi @Guillaume This is now available https://downloads.multiportal.io/installer/multiportal-v1.2.1.tar
I’ve just noticed our guide refers to an older version; I’m updating that now as well. https://docs.multiportal.io/guides/upgrading/offline-update
Woody
MultiPortal has published security advisory MPSA-2026-001, a stored cross-site scripting issue in user and resource name fields.
If you run an affected version, upgrade to 1.2.1 at your next maintenance window. The fix needs no data cleanup: existing names are made safe when they are displayed.
Read the full advisory, including impact, remediation, and workaround:
MPSA-2026-001 on docs.multiportal.io
The fix ships in the 1.2.1 release. To report a vulnerability privately, see Reporting security issues.