Skip to content
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

get not post #1795

Merged
merged 1 commit into from
Jan 10, 2025
Merged

get not post #1795

merged 1 commit into from
Jan 10, 2025

Conversation

emrgnt-cmplxty
Copy link
Contributor

@emrgnt-cmplxty emrgnt-cmplxty commented Jan 10, 2025

Important

Change HTTP method from POST to GET for OAuth callback functions in UsersClient and update version in package.json.

  • Behavior:
    • Change HTTP method from POST to GET for oauthGoogleCallback and oauthGithubCallback in UsersClient.
  • Versioning:
    • Update version in package.json from 0.4.13 to 0.4.14.

This description was created by Ellipsis for 98a0e59. It will automatically update as commits are pushed.

@emrgnt-cmplxty emrgnt-cmplxty marked this pull request as ready for review January 10, 2025 00:52
@emrgnt-cmplxty emrgnt-cmplxty merged commit 47828e2 into main Jan 10, 2025
3 checks passed
Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

👍 Looks good to me! Reviewed everything up to 98a0e59 in 40 seconds

More details
  • Looked at 34 lines of code in 2 files
  • Skipped 0 files when reviewing.
  • Skipped posting 1 drafted comments based on config settings.
1. js/sdk/src/v3/clients/users.ts:545
  • Draft comment:
    Changing the method from POST to GET for OAuth callbacks might expose sensitive information in URLs. Typically, POST is used for such callbacks to ensure data security.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable:
  1. OAuth 2.0 specification explicitly allows and even recommends GET for authorization code callbacks. 2. The parameters being passed (code and state) are designed to be temporary and safe to include in URLs. 3. The code parameter is a one-time use token, and the state parameter is for CSRF protection - both are meant to be in URLs. 4. This is standard OAuth implementation practice.
    I could be wrong about the specific OAuth implementation details of this system. There might be additional sensitive data being passed that I can't see.
    Even if there were additional data being passed, the code shows that only code and state are included as parameters, which are standard URL parameters in OAuth flows.
    The comment should be deleted as it raises an invalid security concern. Using GET with these parameters is actually the standard practice in OAuth 2.0 implementations.

Workflow ID: wflow_LN90Q5wXkyJRhWhY


You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

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