Skip to content

Fido: Fix credential assertion with Chromium-based browsers (add missing public key)#3545

Open
p1gp1g wants to merge 2 commits into
microg:masterfrom
p1gp1g:fido/fix-publicKey
Open

Fido: Fix credential assertion with Chromium-based browsers (add missing public key)#3545
p1gp1g wants to merge 2 commits into
microg:masterfrom
p1gp1g:fido/fix-publicKey

Conversation

@p1gp1g

@p1gp1g p1gp1g commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

That fixes the publicKey field from the authenticationAssertion (when the user makes a credential with FIDO) because:

  • We were maintaining a 2nd list of algorithmInt to Algorithm which was missing -8 (Ed25519) => we never had that Algorithm
  • And once the first point was fixed: we tried to generate Ed25519/Ed448 public keys with the EC KeyFactory, which is not possible - and crashed. We need to generate the PublicKey in another way

Chromium based browsers need that publicKey to accept registrations:

p1gp1g added 2 commits June 8, 2026 21:41
We were maintaining 2 different list of algorithmInt to Algorithm
which led to missing alg (-8). By using EC2Algorithm and RSAAlgorithm
enums directly we avoid further missing algs.
@p1gp1g p1gp1g changed the title Fido/fix public key Fido: Fix credential assertion with Chromium-based browser (add missing public key) Jun 8, 2026
@p1gp1g p1gp1g changed the title Fido: Fix credential assertion with Chromium-based browser (add missing public key) Fido: Fix credential assertion with Chromium-based browsers (add missing public key) Jun 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants