> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/floating-server/floating-server-v2/changelog.md).

# Changelog

<details>

<summary>v2.8.1 – November 17, 2026</summary>

This release adds MySQL as a database and finishes the web UI security changes started in v2.7.0.

**Before you upgrade**

* **Log in again:** everyone is signed out of the web UI once after the upgrade and has to log in once more.
* **Reverse proxy:** if a reverse proxy serves the web UI over plain HTTP, it must pass the browser's `Host` header (for nginx: `proxy_set_header Host $host;`). Otherwise, logins and other changes made in the web UI are refused with `403 cross_origin_request`. Setups where the browser reaches the server over HTTPS are not affected.
* **Browser applications:** the server no longer sends CORS headers, so a browser application on another address can no longer call the API. SDKs, scripts and other clients that send a bearer token are not affected.

**Added**

* **MySQL:** MySQL 8.0.17 or later can be used as the database (`database.type: mysql`), with TLS set through `sslmode` and `sslrootcert`. MariaDB is not supported.

**Changed**

* The web UI no longer keeps its login token in browser storage. The session is held in an `HttpOnly` cookie that page scripts cannot read.
* The server refuses API requests that a browser sends from another website (`403 cross_origin_request`).
* Users with the `user` role no longer see admin-only pages and actions in the web UI: Configuration, User management, Offline/Airgap Licensing, adding or deleting licenses, and other users' release and unregister buttons.
* The API key, shared key and client secret on the Configuration page are write-only. They are never shown again, and an empty field keeps the stored value.
* The web UI's password forms show the password rules and ask for the password twice.
* Built with Go 1.27.4 (CVE-2026-97054) and `golang.org/x/crypto` v0.59.0 (GO-2026-5932).

**Fixed**

* The web UI reported a configuration update as successful when the server had rejected it.
* Unknown URLs in the web UI now show a "Page not found" page.

</details>

<details>

<summary>v2.8.0 – November 10, 2026</summary>

**Added**

* **Connection pool:** database connection pool settings (`MaxOpenConns`, `MaxIdleConns`, `ConnMaxIdleTime`), with a default of 25 open connections.
* **Pool usage endpoint:** administrators can see the pool's usage with `GET /api/v5/db/stats`.

**Changed**

* Idle database connections are reused under load instead of reopened.
* Built with Go 1.27.3.

**Fixed**

* Floating users registering at the same moment can no longer take more seats than the license allows.

</details>

<details>

<summary>v2.7.0 – October 28, 2026</summary>

This release includes all changes since v2.5.1, including v2.5.2, v2.6.0 and v2.6.1. It contains security improvements, and we recommend that all customers upgrade.

**Before you upgrade**

* **Log in again:** all existing sessions end after the upgrade, so every user has to log in once more.
* **Docker volumes:** the standard image no longer runs as root. Before upgrading, change the owner of your existing data volumes with `chown -R 1001:1001 <volume path>`. For the distroless image, use `65532:65532`.
* **Reverse proxy:** if your reverse proxy runs on a different host or container, add it to `server.TrustedProxies`.
* **Swagger:** the `/swagger` page is now turned off by default. To turn it back on, set `server.EnableSwagger: true`.
* **Passwords:** new passwords must be at least 12 characters long and contain at least 3 of the following: lowercase letters, uppercase letters, digits and symbols.

**Added**

* **Local License Server:** a new build for air-gapped environments, released alongside the standard Floating Server.
* **YubiKey selection:** when more than one YubiKey is connected, choose which one to use in the config file or through the admin API.
* **HTTPS support:** the server can serve HTTPS directly. Set `server.TLSCertFile` and `server.TLSKeyFile`.
* **Session limit:** sessions end 7 days after login. Change this with `server.SessionMaxAge`.

**Changed**

* Only admins can view or change the server configuration. Secrets are shown masked.
* Users can register or unregister only themselves on a license. Admins can do this for any user.
* Air-gapped and offline activation codes can be used only once.
* Changing your password signs you out of all other sessions.
* After repeated failed login attempts, the account is blocked for 15 minutes.
* Added security headers, including Content-Security-Policy, HSTS (over HTTPS) and Permissions-Policy.
* Updated Go, third-party libraries and Docker base images.

**Fixed**

* Linux builds run on older systems again (glibc 2.28 or later).
* The config file path can now be absolute as well as relative.
* `sdk.log` is now written next to the executable.
* A clearer error is shown when logging can't be started.
* User errors now return the correct status codes (404, 409) instead of 500.
* The borrow endpoint now accepts the `username` field, as documented.

</details>

<details>

<summary>v2.5.1 – July 23, 2026</summary>

**Fixed**

* Dependency upgrades

</details>

<details>

<summary>v2.5.0 – July 17, 2026</summary>

**Added**

* Added a new Distroless Docker image (`latest-distroless`, `v2.5.0-distroless`) with reduced runtime dependencies and no known CVEs at release; the existing Debian image remains available under `latest` and `v2.5.0` during the initial rollout.

**Fixed**

* Fixed an issue affecting licenses with ID `0`.

</details>

<details>

<summary>v2.4.1 – June 24, 2026</summary>

**Added**

* Improved hardware key verification when multiple smart cards are connected.

</details>

<details>

<summary>v2.4.0 – May 25, 2026</summary>

**Added**

* Support for configuring log file destinations
* Support for Microsoft SQL Server

**Fixed**

* Improved handling of failed license checks
* Fixed installation file handling

</details>

<details>

<summary>v2.3.3 – April 9, 2026</summary>

**Fixed**

* Reset for floating feature consumptions
* Handling of license expiry

</details>

<details>

<summary>v2.3.2 – March 26, 2026</summary>

**Fixed**

* Floating license borrowing problem fixes.

</details>

<details>

<summary>v2.3.1 – March 17, 2026</summary>

**Added**

* Backend logout endpoint.
* Synchronization configuration options for hours and minutes.
* Support for loading the configuration file from `./config/default.yaml` or `default.yaml`.

**Fixed**

* Floating user limit handling, including correct updates for already registered users and enforcement of the maximum allowed users.

</details>

<details>

<summary>v2.3.0 – February 20, 2026</summary>

#### **Added**

* Configurable base path prefix (BasePath).
* High availability support via Kubernetes (multiple replicas) and SDK-side load balancing.

#### **Fixed**

* Consumption calculation fixes.
* Fixes for floating features behavior.
* Fixes for port configuration/customization.

</details>

<details>

<summary>v2.2.0 – December 24, 2025</summary>

#### Added

* Hardware Key Support: FSv2 can be provisioned with a hardware key and can manage hardware-key compatible licenses and bundles.
* Docker logging mode (logs to stdout)

#### Fixed

* Bug fixes and minor improvements

</details>

<details>

<summary>v2.1.0 – November 26, 2025</summary>

#### Added

* Offline refresh functionality
* Support for full SQLite database encryption using SQLCipher
* Optimized database performance, increasing concurrency capabilities
* Bundle license features visible in the UI

#### Fixed

* Various bugs

</details>

<details>

<summary>v2.0.0 – October 6, 2025</summary>

#### Added

* TLS support for PostgreSQL – Secure database connections are now supported
* Helper scripts – Added scripts to run PostgreSQL with TLS and Docker Compose for simplified setup
* Automatic config generation – Configuration files can now be generated directly from the LicenseSpring platform
* Simplified provisioning – Uses a single certificate for both server and client, reducing setup complexity

#### Fixed

* Restricted the Floating Server to offline floating licenses only
* Various UI bugs and usability issues

</details>

<details>

<summary>v2.0.0-beta.2 – September 5, 2025</summary>

#### Added

* Restricted license activation to Offline Floating Licenses only
* Official Docker image: licensespring/floating-server-v2:v2.0.0-beta.2

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.licensespring.com/floating-server/floating-server-v2/changelog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
