Skip to content

fix(webauthn): missing passkey finish tooling #443

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 11, 2025

Conversation

james-d-elliott
Copy link
Member

@james-d-elliott james-d-elliott commented Jul 11, 2025

This includes a function similar to ValidatePasskeyLogin and FinishDiscoverableLogin. This allows both validating a discoverable credential and deterministically finding the user in question. This is effectively missing tooling making it more difficult for people to perform this specific action.

This includes a function similar to ValidatePasskeyLogin and FinishDiscoverableLogin.
@james-d-elliott james-d-elliott requested a review from a team as a code owner July 11, 2025 02:48
Copy link

coderabbitai bot commented Jul 11, 2025

Walkthrough

The update refactors several login-related methods in the WebAuthn module to use named return variables and explicit response variable declarations. A new method, FinishPasskeyLogin, is introduced to handle passkey logins. The authenticator counter update in the internal validation logic is moved to occur after backup flag checks, and related error messages are clarified.

Changes

File(s) Change Summary
webauthn/login.go Refactored method signatures to use named return variables; added FinishPasskeyLogin; moved authenticator counter update after backup flag checks; clarified error messages.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant WebAuthn
    participant Handler
    participant Authenticator

    Client->>WebAuthn: Send login/passkey request (response)
    WebAuthn->>WebAuthn: Parse response
    alt Passkey login
        WebAuthn->>Handler: Lookup user (if discoverable)
        WebAuthn->>WebAuthn: ValidatePasskeyLogin
    else Regular login
        WebAuthn->>WebAuthn: ValidateLogin
    end
    WebAuthn->>Authenticator: Check backup flags
    WebAuthn->>Authenticator: Update counter (after flag checks)
    WebAuthn-->>Client: Return user, credential, error
Loading

Poem

A bunny hops through code so bright,
Refactors methods left and right.
Passkey logins join the show,
Authenticator counters move below.
With clearer words and tidy flow,
This WebAuthn is good to go!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cb74620 and 62b0643.

📒 Files selected for processing (1)
  • webauthn/login.go (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Analyze (go)
🔇 Additional comments (7)
webauthn/login.go (7)

199-207: LGTM - Good refactoring to named return variables

The refactoring to use named return variables improves code readability and follows Go best practices. The explicit declaration of parsedResponse before parsing is also a good practice that makes the code more maintainable.


212-220: LGTM - Consistent refactoring pattern

The changes maintain consistency with the FinishLogin method refactoring, using the same pattern of named return variables and explicit variable declaration.


222-233: LGTM - Well-implemented new method following established patterns

The new FinishPasskeyLogin method correctly follows the established pattern of the other Finish* methods while appropriately returning both user and credential for passkey authentication. The implementation properly delegates to ValidatePasskeyLogin and handles error cases consistently.


236-246: LGTM - Consistent method signature update

The method signature update maintains consistency with the other refactored methods while preserving the existing logic and error handling.


392-392: LGTM - Improved error message clarity

The error message is more descriptive and clearly indicates the nature of the backup flag inconsistency issue.


397-397: LGTM - Clear and specific error message

The error message clearly explains the invalid flag combination (BE=0 and BS=1), making it easier for developers to understand the validation failure.


400-401: LGTM - Security improvement by moving counter update

Moving the authenticator counter update to after the backup flag validation is a security improvement. This ensures that the counter is only incremented after all validations pass, preventing counter manipulation through failed validation attempts.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@james-d-elliott james-d-elliott changed the title refactor: include finish passkey login function fix(webauthn): missing passkey finish tooling Jul 11, 2025
@james-d-elliott james-d-elliott merged commit 088d7c4 into master Jul 11, 2025
6 checks passed
@james-d-elliott james-d-elliott deleted the refactor-missing-method branch July 11, 2025 02:50
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