Skip to content

fix(typecheck): close auth/sqlit/wallet type and API gaps#39

Open
Dexploarer wants to merge 1 commit intoJejuNetwork:developfrom
Dexploarer:codex/pr-auth-typecheck
Open

fix(typecheck): close auth/sqlit/wallet type and API gaps#39
Dexploarer wants to merge 1 commit intoJejuNetwork:developfrom
Dexploarer:codex/pr-auth-typecheck

Conversation

@Dexploarer
Copy link
Contributor

Summary\n- close auth provider gaps for credential mapping and VC attestation conversion\n- harden passkey response encoding in auth SDK client\n- improve external login flow in CLI with address+signature mode\n- make wallet linked provider typing exclude unsupported email/phone entries\n- harden SQLit row normalization for empty query results\n- add monitoring package dependency on @jejunetwork/auth\n\n## Validation\n- bun run --cwd packages/auth typecheck\n- bun run --cwd packages/sqlit typecheck\n- bun run --cwd apps/wallet typecheck\n- bunx pyright packages/training/python apps/dws/api (pre-existing unrelated errors remain)\n- bun run typecheck:rust

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c955ae4988

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 274 to 275
const nonce = bytesToHex(randomBytes(32))
const timestamp = Date.now()

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Reuse the signed challenge for external login

The external flow rebuilds message with a fresh random nonce/timestamp before checking options.signature, so the second invocation cannot verify the signature from the first invocation's printed message. In the two-step flow (--external --address first, then --external --address --signature), verifyMessage will always fail because the signed payload changed between runs.

Useful? React with 👍 / 👎.


logger.info('Then run:')
logger.info(
`jeju login --network ${network} --address ${address} --signature <your-signature>`,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Include --external in the follow-up login command

The suggested command omits --external, so users following this prompt run the non-external branch where --signature/--address are ignored and private-key auth is attempted instead. This makes the documented external workflow fail (or authenticate as a different local key if one is configured) even when the user provides a valid external signature.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant