Skip to content

v1.10.1

Latest

Choose a tag to compare

@chr0nzz chr0nzz released this 15 Aug 04:42

v1.10.1

Features

  • CrowdSec mTLS - authenticate the LAPI with a client certificate instead of, or alongside, the bouncer key and machine login (#131).

  • OIDC automatic sign-in - opt-in setting under Settings -> Authentication -> OIDC

  • Redesigned setup wizard - a 1080px two-pane page with a step sidebar

  • Static Config placement - the on/off toggle becomes Off, Settings or Tab under Settings -> Interface.

  • CrowdSec reads only what changed - decisions come from the LAPI's streaming endpoint: the full set once, then only deltas on refresh. Falls back to the paged read on an older LAPI (#131).

  • CrowdSec timeouts and alert volume are configurable - CROWDSEC_READ_TIMEOUT, CROWDSEC_CONNECT_TIMEOUT and CROWDSEC_ALERT_LIMIT (default 500 most recent, 0 for all). Host and agents.

  • Acknowledge external authentication - the "no authentication" banner can be acknowledged under Settings -> Authentication when a forward-auth provider already protects TM (#133). Changes what you are told, never what is enforced.

  • Middleware templates moved - manage them from the middlewares toolbar as a slide-in panel, and start a new middleware from a template in the Add form.

  • Settings search - one box filters the active pane by name, description or value, with match counts on the other panes. Drives the Static Config filter when that shows in Settings.

Fixes

  • Backup retention was rendered as two fields bound to the same value, so editing one silently changed the other
  • Saving the Providers section destroyed every providers.docker and providers.file key the form does not manage. It now merges
  • CrowdSec alert rows for simulated and unbanned sources never showed their yellow marker
  • CrowdSec and Logs: card links that only change the list below the fold looked dead. They now scroll to it (#130)
  • CrowdSec: the feed could get stuck on Bans in force with no visible way back (#130)
  • CrowdSec: the alert read asked for every alert ever stored, which timed out on large instances (#131)
  • CrowdSec: a timeout partway through reading decisions threw away every page already read
  • Agent CrowdSec client certificate paths were discarded when the agent was saved
  • The agent's CrowdSec client had no timeout, so a stalled LAPI could hang requests indefinitely
  • The CrowdSec tab on an agent said only "not configured", pointing at the wrong container
  • CrowdSec: adding a decision left the form open after a successful save
  • An expired session made every list render empty instead of returning you to the login page, because API calls answered with a redirect to the login page rather than a 401
  • Agent static config backups were invisible: the Backups window hid the Static Config tab for agents and mixed their traefik.yml backups into the dynamic list
  • Restoring a static config backup overwrote the dynamic config with traefik.yml, on the host and on agents. A backup whose name matches no config file is now refused instead of guessed at
  • A route whose app icon failed to load left an empty square. It now falls back to a monogram
  • A middleware wizard field containing a quote or a backslash produced invalid YAML and the save failed. Values are now escaped
  • Adding, deleting or clearing notifications rejected API key requests with a CSRF error, even though API keys are documented to skip CSRF
  • API reference: about 30 endpoints were undocumented, and the docs never stated what an expired session returns. A test now fails the build when an endpoint is missing from either the reference or the OpenAPI spec
  • Settings on a phone opened straight into Interface instead of the list of panes, so there was no way back to it without the back arrow
  • Between 640px and 768px wide, Settings showed the phone list and the desktop sidebar at once, with no pane at all
  • ph-plug-slash and ph-server are not in the bundled icon font, so "Traefik API not reachable" and the service backend counts rendered a blank box
  • Settings section headings were unstyled outside the modern layout: the icon sat against the label with no gap and the rule line was missing
  • The release notes in Settings - About rendered GitHub alerts as a literal [!IMPORTANT] line above the text, because each quoted line became its own box. Alerts now render as one callout with an icon, and the panel is more than twice as tall
  • Settings was only ever styled for the Modern layout. On Classic, every description was truncated to one line with an ellipsis and the Layout row collapsed onto itself, with the "Classic is being phased out" note overlapping the Classic/Modern buttons. The modal now looks the same in both layouts