Repository navigation
5.5.5
November 17, 2026
Summary
This release reworks authentication and access. The AUTH ENV is replaced by SITE_ACCESS (public, optional, required) and AUTH_PROVIDERS, login providers become plugins (local, proxy — formerly csso — and a new ldap provider for OpenLDAP and Active Directory), and access is granted with roles at global, mission and layer scope to accounts, groups and audiences, managed on Configure's new Users & Access page. Long-term tokens can be limited to missions and capabilities, AUTH_TOKENS controls who may create them, and signed-in users can manage their own token from the main site's account menu. Existing accounts, passwords, sessions and tokens are kept, and their access is imported once.
The raster stack moves to TiTiler 2.x / TiTiler-pgSTAC 3.x / rio-tiler 9.x (pinned identically for Docker Compose and non-Docker installs), with expression parsing on the /titiler and /titilerpgstac proxies and custom GDAL color tables for COG layers. The Docker image runs as an unprivileged user (default uid/gid 10001) and works for any uid set with Compose user:. The landing page is redesigned with admin-configurable mission cards, DrawTool files are scoped to the mission they were made in, a shared Missions/shared folder is readable by every signed-in user, and the new Broadcast plugin lets admins or pipelines push layer refreshes to connected clients. Geodatasets gain statistics and Style-tab dynamic vector styling, layer types and attachments are fully pluginized, Leaflet is upgraded to 1.9.4, mobile mode gains a bottom sheet and more tools, and server defaults for CORS, cookies and request limits are updated.
Compatibility
- Mission configurations: Backward compatible. Existing
cogBands,cogColormapand expression settings continue to work; legacyasset_bNexpressions are mapped tobN. No mission config changes are required. - JavaScript API (
window.mmgisAPI): Backward compatible. AddsmmgisAPI.setLayerAttachmentConfig. - End users: Mostly unchanged. Login and mission access behave as before; the landing page and login form look different, and new DrawTool files are listed only in the mission they were created in (files made before this release are still listed everywhere by default).
- Deployments: Breaking.
AUTHand theCSSO_*ENVs must be replaced, the database must be backed up before upgrading, Docker deployments need the updateddocker-compose(new TiTiler images, renamedtitiler-pgstacENVs, new container uid), and non-Docker installs must reinstall Python dependencies. See the migration guide below. - Plugin developers: Breaking for layer type and attachment plugins. See the migration guide below.
Migration Guide
- Breaking (Deployments): Back up the database before upgrading; downgrading means restoring that backup. Accounts' access is imported once from the legacy
users.permission,missions_managingandmissions_viewingcolumns into role bindings. After that the columns are left as they were and are no longer read or updated, so running an older release on the upgraded database is not supported. See Auth & access migration. - Breaking (Deployments):
AUTHandCSSO_*ENVs removed. MMGIS refuses to start whileAUTH,CSSO_GROUPS,CSSO_LEAD_GROUPorCSSO_PROXY_SECRETis set. Earliersample.envfiles set theCSSO_*lines on every site, so delete them even if the site never used CSSO. SetSITE_ACCESSandAUTH_PROVIDERSinstead. See Auth & access migration. - Breaking (Deployments): TiTiler / TiTiler-pgSTAC / TiPG versions.
titiler.application0.24 → 2.2.0,titiler-pgstac1.9 → 3.1.0,tipg1.3 → 1.6.1,rio-tiler7.x → 9.x. Update both the Compose images (ghcr.io/developmentseed/titiler:2.2.0,ghcr.io/stac-utils/titiler-pgstac:3.1.0,ghcr.io/developmentseed/tipg:1.6.1) and the Python environment (python-requirements.txt/python-environment.yml).pypgstacstays at 0.9.6; no pgSTAC schema migration is required beyond thepypgstac migrateMMGIS already runs on startup. - Breaking (Deployments): titiler-pgstac ENVs renamed.
POSTGRES_USER/PASS/HOST/PORT/DBNAME→PGUSER/PGPASSWORD/PGHOST/PGPORT/PGDATABASEfor thetitiler-pgstacservice (Compose andadjacent-servers/titiler-pgstac/.env.example). Thestacandtipgservices keepPOSTGRES_*. The unusedWORKERS_PER_CORE/MAX_WORKERSentries were removed (the image only honorsWEB_CONCURRENCY). - Breaking (Deployments): The MMGIS container runs as non-root, default uid/gid
10001. Bind-mounted./Missions(and./ssl) must be writable by the container's uid: either setuser: "<uid>:<gid>"on themmgisservice to the existing owner (e.g. fromstat -c '%u:%g' ./Missions) or chown them to10001. Addgroup_add: ["0"]if that uid must also write inside the image (e.g. saving a mission back to its blueprint template,SPICE_SCHEDULED_KERNEL_DOWNLOAD=truewithout a bind-mountedspice/kernels, or file logs inAPI/logs). Sites that build their own image can still set--build-arg APP_UID/APP_GID. - Breaking (Deployments):
_docker-entrypoint.shremoved. Compose files or scripts that setentrypoint/commandto./_docker-entrypoint.shshould usenpm run start:prod-dockerinstead (or drop the override). - Breaking (Deployments): Same-origin by default. Cross-origin browser clients and websocket connections must be listed in
CORS_ORIGINS(comma-separated); unset, MMGIS allows same-origin requests only. WhenHTTPS=true, session cookies default toSecure; setSESSION_COOKIE_SECURE=falseonly for intentionally non-TLS deployments. - Changed (Deployments): Request limits. The global request body limit is 10mb (500mb on
/api/configure,/api/datasets,/api/files,/api/geodatasets; 50mb on/api/draw), and the global/api/rate limit is 3000 requests per 5 minutes per IP. - Breaking (API):
/api/accounts/updateand/api/users/signuptakeviewing(null: every mission; a list: only those) instead ofmissions_viewing./api/accounts/updaterefuses requests that still sendrole,missions_managingormissions_viewing; grant roles with/api/access/bindings/add./api/accounts/entriesno longer returnsmissions_managingormissions_viewing. - Breaking (API): changed responses for scripts.
/api/configure/user-permissionsno longer returnspermission; it returnsrole,superadminandcapabilities./api/longtermtoken/getno longer returnscreated_by_permissionorcreated_by_missions./api/longtermtoken/generatetakesperiodas milliseconds or"never"; strings such as"1d"are refused. - Breaking (Direct TiTiler API users): TiTiler 2.x request/response changes. For
/titilerpgstac:bidx/expressionper asset are now expressed asassets=asset|bidx=1,2andassets=asset&expression=b1*2(top-levelbidxis ignored;asset_b1syntax,asset_bidx,asset_expression,vrt://assets are removed);/pointresponses return{coordinates, assets:[{name, values, band_names}]}instead of top-levelvalues. For both services:@2x/tile_scaleURL suffixes are removed in favor oftilesize=. MMGIS's own frontend has been updated; external clients calling the proxies directly must update. - Changed (API): TiTiler
expressionparsing. The/titilerand/titilerpgstacproxies now accept only band identifiers, numeric literals, arithmetic/comparison/logical operators, function calls such aswhere()/sqrt(), parentheses, commas and;. Other content returns400. - Breaking (Plugin Developers): Layer type and attachment contract. The unused
loadop is removed (data acquisition belongs to core'ssourcesurface), surfaces live one per file (map.js,config.js,filter.js,globe/{cesium,lithosphere}.js), and core decisions come from manifestcapabilitiesvalidated against a schema. Seeplugins/core/layertypes/README.mdandplugins/core/layerattachments/README.md. - Changed (Plugin Developers): Leaflet 1.5.1 → 1.9.4. Leaflet is now an npm dependency instead of a vendored copy;
window.Lis unchanged. Plugins using Leaflet internals or the.leaflet-clickableclass should be checked. - Added (Plugin Developers): Auth provider and connection plugins. Login providers live in
plugins/core/auth/<Name>/and service connections inplugins/<container>/connections/<Name>/. See AuthProviders and Connections.
Added
- Auth & access:
SITE_ACCESSandAUTH_PROVIDERS, auth provider plugins (local,proxy), named roles and capabilities granted to accounts, groups and audiences at global, mission or layer-subtree scope, Configure's Users & Access page, and token v2 with mission and capability limits (PR #1146) - LDAP login provider (OpenLDAP, Active Directory) with provider-linked account lifecycle, and one shared login form for username/password providers across the login page, Configure and the in-app modal (PR #1155)
AUTH_TOKENS=all|adminsto allow or prevent non-admin accounts from creating API tokens, per-account token limits, and an API token menu in the main site's account menu (PR #1164)- Landing page redesign (React) with admin-configurable mission cards, mission status and General Options (PR #1079)
- Shared
Missions/sharedfolder readable by any signed-in user or valid long-term token (PR #1121) - Broadcast plugin:
POST /api/broadcast/layerUpdatetells connected clients to refresh layers (PR #1071) - Geodataset statistics (per-group and dataset-wide) and dynamic vector styling from the Style tab (PR #1044)
- Custom GDAL color tables for COG layers (
cogColormapJson) via TiTiler (PR #1017) - On-map attribution dropdown gated by
look.showAttributionsOnMap, and attributions in each layer's info modal (PR #1088) - Legend Tool highlights the entry matching the value the Identifier resolves under the cursor (PR #1087)
- Configure: rename a mission, optionally moving its folder (PR #1030, PR #1041)
- Configure: a component's
plugin.jsondisplay_namelabels its Components card (PR #1162) - DrawTool: per-mission "Show Files Without a Mission" and "Show Lead Files" settings, and leads can move a file to another mission (PR #1094)
- Mobile mode: bottom sheet with three stops per tool (PR #1046),
worksOnMobiletool flag (PR #1047), compact OperationsClock (PR #1048) and AnimationTool support (PR #1106) - Layer types and attachments: single-file plugins, manifest
capabilities, attachmentonConfigChangeandmmgisAPI.setLayerAttachmentConfig, interactionconfigPath, npm dependencies, andcreate layerattachmentin the plugin CLI (PR #1036) - Expression parsing middleware for the TiTiler and TiTiler-pgSTAC proxies (
adjacent-servers/validateTitilerExpression.js) (PR #1084)
Changed
- Pinned TiTiler 2.2.0, TiTiler-pgSTAC 3.1.0, TiPG 1.6.1 and rio-tiler 9.x in Docker Compose and Python requirements; STAC tile, terrain and point requests use the TiTiler 2.x
assets=asset|bidx=syntax; expression help text documentsbNband syntax (PR #1084) - Dockerfile runtime user is
mmgiswith default uid/gid10001, created withuseradd --no-log-init;/usr/src/appis owned bymmgis:0withg=u; themmgismicromamba environment is activated viaENVso it applies to any runtime uid; the image starts withCMD ["npm", "run", "start:prod-docker"]; Numba and npm caches point at/tmp;docker-compose.sample.ymldocuments the optionaluser:override (PR #1084, PR #1120) - DrawTool files are tagged with the mission they were created in and listed only in that mission (PR #1094)
- Leaflet is an npm dependency at 1.9.4 instead of a vendored 1.5.1, and every remaining vendored Leaflet file documents why (PR #1043)
CORS_ORIGINSapplies to both HTTP and websocket connections, session cookies setsameSiteand honorSESSION_COOKIE_SECURE, and request body and rate limits are configured per route (see the Migration Guide); dependency updates (PR #1051)- Coordinates display wraps longitude to -180..180 (PR #1057)
- Pinned
stac-fastapi-api/types/extensionsto 6.2.1 (PR #1061) - CI runs on Node 22 (PR #1059)
- Development startup logs are no longer cleared from the terminal (PR #1029)
- Development console logger strips newlines from the caller (PR #1122)
Fixed
npm run auth:migrate, including--dry-run, works on databases from 5.2.24 and earlier, which have nousers.missions_viewingcolumn- Builds and Docker images keep npm packages at their
package-lock.jsonversions when plugin dependencies are installed, which restores the Layers tool's per-layer settings and download panels in production builds - Globe: Identifier values when the map and globe are unlinked, wrong values on STAC layers with many items, "no data" instead of 0, throttled point queries, tile error noise, and 3D Tiles layers in the Layers tool (PR #1149)
- Landing page: hidden-mission URLs (PR #1149), logout giving no feedback (PR #1098), and a
PUG:NO_END_BRACKET500 on/in production builds (PR #1096) FORCE_CONFIG_PATHis read at runtime in production builds (PR #1161)- COG tile layers with
s3://URLs were treated as mission-relative (PR #1099) - Geodatasets: queries on tables created before temporal support, start-only time filters dropping features, and recreating with new time mappings (PR #1049)
- LithoSphere globe layer operations, a vector time-filter race, and the time-tile availability histogram (PR #1050)
- Global Search autocomplete reaches every unique value, not only the first 500 or a random sample on large geodatasets (PR #1132; also in 5.2.24-a)
- Header layers added through the Configure API without
sublayersget an empty array (PR #1133) - Duplicated Projection Setup actions in the Coordinates tab (PR #1109)
GET /api/webhooks/entrieshung when no webhook configuration existed (PR #1093)- Mission data paths in the Viewer, Identifier and Measure tools use the mission folder instead of the display name (PR #1039)
- Console errors on missions without a globe (PR #1042)
- Hidden scalebar text in mobile mode (PR #1105)
- Dropy dropdowns and the search component in Maker (PR #1033)
pypgstac migrateon startup is run fromPATHand receivesHOME, so it works in venv installs and under a custom container uid (PR #1084, PR #1120)- TiTiler colormap legend images are requested with
f=png(PR #1084) - An unwritable SPICE kernel directory is logged as an error instead of crashing MMGIS on startup with
SPICE_SCHEDULED_KERNEL_DOWNLOAD_ON_START=true(PR #1120)