You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/sensu-go/6.13/release-notes.md
+16-25Lines changed: 16 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ version: "6.13"
9
9
menu: "sensu-go-6.13"
10
10
---
11
11
12
-
-[6.13.1 release notes](#6130-release-notes)
12
+
-[6.13.1 release notes](#6131-release-notes)
13
13
-[6.13.0 release notes](#6130-release-notes)
14
14
-[6.12.0 release notes](#6120-release-notes)
15
15
-[6.11.0 release notes](#6110-release-notes)
@@ -119,30 +119,21 @@ Read the [upgrade guide][1] for information about upgrading to the latest versio
119
119
120
120
---
121
121
122
-
## 6.13.1 — October 29, 2025
123
-
The latest release of Sensu Go, version 6.13.1, is now available for download.
124
-
Read the [upgrade guide][1] to upgrade Sensu to version 6.13.1.
125
-
126
-
### New Features
127
-
- Added `access-token-expiry` backend configuration variable to control expiry of access tokens.
128
-
*(The duration must be specified in minutes, e.g., `access-token-expiry: 1440m`)*
129
-
- Added `refresh-token-expiry` backend configuration variable to control expiry of refresh tokens.
130
-
*(The duration must be specified in minutes, e.g., `refresh-token-expiry: 10080m`)*
131
-
132
-
### Improvements
133
-
- Introduced fine-grained token expiry control via new backend configuration options.
134
-
- Enhanced backend configurability to support environments requiring custom session lifetimes.
135
-
136
-
### Fixes
137
-
- Minor improvements and optimizations applied to backend configuration handling.
138
-
-**Silence Creation Issues**: Fixed a bug where users were unable to create silences via the `curl` command when `max-silenced-expiry-time-allowed` and `default-silenced-expiry-time` flags were not set in `backend.yml`. These flags are now optional, allowing silences to be created via Web UI, `sensuctl`, and API without requiring these fields.
139
-
-**UID Mapping Issues in Docker (RedHat and Alpine)**: Resolved a compatibility issue where Sensu Docker containers failed to run on systems using cgroupsv2, due to a file (`etcdctl`) having a UID exceeding the 65535 limit. All UIDs are now within the allowed range to support UID remapping and avoid container runtime errors.
140
-
-**OIDC Integration Improvements for Microsoft Entra ID**: Resolved an issue where users were prompted for approval on every login when using Microsoft Entra ID as the OIDC provider. The login experience is now smoother, with Entra ID respecting previously granted permissions and reducing unnecessary approval prompts.
141
-
142
-
### Removals
143
-
-**Removed Tessen Telemetry Service**:
144
-
The Tessen functionality has been removed from Sensu Go. Tessen previously collected and transmitted anonymized usage data to Sensu for product insights. Since the backend infrastructure supporting telemetry collection is no longer available, Tessen has been fully deprecated and removed from this release.
145
-
Documentation related to Tessen has been updated or removed accordingly.
122
+
## 6.13.1 release notes
123
+
124
+
**October 29, 2025**— The latest release of Sensu Go, version 6.13.1, is now available for download.
125
+
126
+
**FIXES**
127
+
128
+
- Silence Creation Reliability:
129
+
- Fixed an issue where users were unable to create silences via curl when the max-silenced-expiry-time-allowed and default-silenced-expiry-time flags were not set in backend.yml.
130
+
- These configuration flags are now optional, allowing silences to be created via the Web UI, sensuctl, and the API without requiring these fields to be configured.
131
+
- Docker UID Mapping on cgroupsv2 (Red Hat & Alpine)
132
+
- Resolved a compatibility issue that caused Sensu Docker containers to fail on systems using cgroupsv2, due to the etcdctl binary being assigned a UID above the 65535 limit.
133
+
- All container file UIDs are now within the allowed range, ensuring UID remapping works correctly and preventing container runtime failures on affected Red Hat and Alpine environments.
134
+
- OIDC Integration with Microsoft Entra ID
135
+
- Fixed an issue where users were prompted for admin consent/approval on every login when using Microsoft Entra ID as the OIDC provider.
136
+
- The OIDC flow has been updated so that previously granted permissions are respected, providing a smoother login experience and eliminating unnecessary approval prompts for returning users.
0 commit comments