RocketChat / RocketChat/Rocket.Chat

iOS - Using custom OAuth2 that signs in via Entra ID, passkey saved in authenticator app is not available to sign in

Open
#38,734 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: bug
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

I am currently using Authentik as my OIDC/OAuth2 provider, I've followed the documentation outlined here:
https://integrations.goauthentik.io/chat-communication-collaboration/rocketchat/

I am using Entra ID to sign into authentik.

When I go to sign into my rocket chat tenant via the iOS app, and choose my SSO login, it opens the Entra ID sign in but does not prompt to choose a passkey when I select security key. Provides error message seen below.

Steps to reproduce:
  1. Setup Custom OAuth2 Provider in Rocket.chat for Authentik as per documentation above
  2. Install latest iOS rocket.chat app -> enter tenant info -> choose SSO login button
  3. Redirect to Entra ID sign in -> Choose Face, Fingerprint, PIN or Security Key -> "Your device will open a security window" appears for a second (normally this would be where it would redirect to authenticator app) -> Receive error message "We couldn't sign you in, Something went wrong when trying to sign in with a passkey."
Expected behavior:

On Entra ID sign in redirect within iOS App - > Choose Face, Fingerprint, PIN or Security Key -> App opens a security window to choose my passkey for my Entra ID account in my authenticator app.

Actual behavior:

Redirect to Entra ID sign in -> Choose Face, Fingerprint, PIN or Security Key -> "Your device will open a security window" appears for a second (normally this would be where it would redirect to authenticator app) -> Receive error message "We couldn't sign you in, Something went wrong when trying to sign in with a passkey."

Server Setup Information:
  • Version of Rocket.Chat Server: 8.1.0
  • License Type: Starter
  • Number of Users: 1 [testing enviroment]
  • Operating System: Linux Debian 13.1
  • Deployment Method: docker compose
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Mongo
  • NodeJS Version: 22.16.0 - x64 [container]
  • MongoDB Version: 8.2.4 [container]
Client Setup Information
  • iOS App: 4.69.0.108207
  • Operating System: iOS 26.3
Additional context

If I open my tenant via a web browser on my phone, it redirects properly and allows me to use my passkey as expected. The issue is specifically for the iOS app. I have not tested android.

Relevant logs

N/A

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the SSO flow in the iOS app using Authentik backed by Entra ID, following the listed setup and client versions. Compare the failing in-app passkey flow with the working mobile-browser flow, then identify the iOS app entry point handling SSO and passkeys. Done means the Entra ID sign-in can open the authenticator passkey prompt in the app.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios
Domain
authentication, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.