Hey y’all,
OttoFMS 4.15.0 was just released! Our first version of 2026 is a heavy hitter, big features are:
- Google Groups authentication is back! One of the last features of Otto v3 that had not been ported over, setup in OttoFMS is easier and faster than Otto v3’s setup was. This allows you to use Google as a custom IdP with group support (not natively provided with FileMaker). Check out the Google Groups OAuth docs for setup details.
- Data API Keys can now be used for multiple FileMaker files! During setup or when editing an API key you can now give it access to multiple files. All files must have the same username/password on them for this to work and the account must have REST or OData permissions (depending on if setting up data api or odata access) on all files. There is also a new key by key option to allow access to databases that you did not define for that key, which lets you use a single key on any database that account has access to, without the need to go make changes to the Data API Key each time.
- Hosted FileMaker Files can now be downloaded directly from the File Browser. No more confusing “go over to the FileMaker Admin tab to download that” ever again! As an added bonus, this also lets you send a download link for a hosted file to someone else.
- The File Browser has a number of other updates and fixes, check out the changelog for all the details.
- The MCP Server UI has gotten spruced up a bit with new functionality to duplicate MCP Server or Tools, Import and export Servers or tools, and make edits to your servers after creation.
- Additionally this version has a number of bug fixes and optimizations, check out the full changelog for details.
Check out the updating OttoFMS docs to instructions on updating to the new version, and as always let us know if you have any issues.
One note: This version does not address the issues on Linux ARM, if you have any issues on Linux please add a note on the pertinent thread here in the community. It makes it easier for me to update y’all if all the notes on that are in a single thread rather than spread across multiple version release threads. I plan on doing a deep dive into these issues in the coming weeks and should have an update for y’all soon.
-Kyle
