A post quantum option for the LINE Login id token verification

Open
#194 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
18/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, java

Research direction

Start with IdTokenParser and the jjwt key resolver that builds EC and RSA keys from the JWKS, then check the JWKS parsing code that feeds it. Confirm whether the jjwt version in use can verify ML-DSA at all before writing anything. Done would mean an ML-DSA key in a JWKS verifies a token in the existing ID token tests, using the external test vectors the issue links. The issue depends on a service that does not yet issue such tokens, and it is an unsolicited vendor offer, so get maintainer direction first.

Written by the indexing model from the issue text.

Description

On Android the id token check runs through IdTokenParser with jjwt and a key resolver that only builds EC and RSA keys from the JWKS. Same classical story as everywhere else.

ML DSA from FIPS 204 sits in JOSE under RFC 9964. Teach the key resolver and the JWKS parsing to handle an ML DSA key and the Android SDK verifies a post quantum id token once the service issues one.

Vectors to check it against are at https://github.com/quantova-inc/pq-sign-vectors. Happy to draft it under your agreement.

[email protected]

Dominant language
Java
Stars
149
Forks
55
PR merge metrics
No merged PRs in 30d

Getting set up

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.

More from line/line-sdk-android

All issues in line/line-sdk-android

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.