keycloak/keycloak

Device activity does not recognize iOS 26 correct

Open

#44741 opened on Dec 8, 2025

View on GitHub
 (7 comments) (2 reactions) (0 assignees)Java (34,398 stars) (8,346 forks)batch import
area/account/uihelp wantedkind/bugpriority/lowstatus/auto-expirestatus/expired-by-botstatus/reopenedteam/core-authnteam/core-clients

Description

Before reporting an issue

  • I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

No response

Describe the bug

Hi,

iOS 26.1 is recognized as iOS 18.7 in device activity. Mobile safari is correct with version 26.1.

Version

26.4.7

Regression

  • The issue is a regression

Expected behavior

iOS should be recognizes as version 26.1.

Actual behavior

It shows version 18.7

How to Reproduce?

  • install keycloak 26.4.7
  • log in with iPhone with iOs 26.1

Anything else?

No response

Contributor guide

Tech stack
javarest api
Domain
backendsecurity
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Javabasic understanding of user agent parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
The issue reports incorrect iOS version detection in device activity. Look for user agent parsing logic in the Keycloak codebase, likely in classes handling device metadata or client details. Check the UserAgentParser or similar utility that maps user agent strings to OS versions. The bug is that iOS 26.1 is being displayed as 18.7, suggesting a regex or mapping error. You may need to examine the version extraction pattern for iOS and verify with Safari's user agent string. The issue comments may provide additional context, but the fix is likely localized to the parsing logic.