Skip to content

Conversation

@douxc
Copy link
Contributor

@douxc douxc commented Jan 7, 2026

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Screenshots

Before After
... ...

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran make lint and make type-check (backend) and cd web && npx lint-staged (frontend) to appease the lint gods

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @douxc, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the security posture of the web application's login mechanisms. By implementing client-side encryption for both email verification codes and user passwords, it ensures that sensitive authentication data is protected from potential interception during transit, thereby bolstering user data privacy and system integrity.

Highlights

  • Enhanced Security for Email Login: The verification code used for email-based login is now encrypted on the client-side before being sent to the server, adding an extra layer of security.
  • Password Encryption for Web App Login: User passwords for the web application login are now encrypted client-side prior to transmission, protecting sensitive credentials during the login process.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces client-side encoding for the web app login verification code and password. However, the implementation uses Base64 encoding, which is a form of data obfuscation, not cryptographic encryption. This is a significant concern as it can create a false sense of security, and the function names (encrypt...) are misleading. My review comments highlight this security issue and recommend either using proper encryption or renaming the functions to accurately reflect their behavior (e.g., encode...) to avoid security misconceptions.

@douxc douxc changed the title Fix/web app login code encrypt Fix:web app login code encrypt Jan 7, 2026
@douxc douxc marked this pull request as ready for review January 8, 2026 02:01
@douxc douxc requested a review from iamjoel as a code owner January 8, 2026 02:01
Copilot AI review requested due to automatic review settings January 8, 2026 02:01
@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jan 8, 2026
@douxc douxc changed the title Fix:web app login code encrypt fix: web app login code encrypt Jan 8, 2026
Copy link
Contributor

@GareArc GareArc left a comment

Choose a reason for hiding this comment

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

lgtm

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jan 8, 2026
@GareArc GareArc merged commit c5b99eb into main Jan 8, 2026
18 of 20 checks passed
@GareArc GareArc deleted the fix/web-app-login-code-encrypt branch January 8, 2026 02:04
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This pull request attempts to add password and verification code encryption to the web app login flow using Base64 encoding. However, it introduces critical breaking changes that will prevent all web app logins from working.

  • Adds encryptPassword() call to password field in web app email/password login
  • Adds encryptVerificationCode() call to code field in web app email code login
  • Imports encryption utilities from @/utils/encryption

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
web/app/(shareLayout)/webapp-signin/components/mail-and-password-auth.tsx Encrypts password before sending to backend
web/app/(shareLayout)/webapp-signin/check-code/page.tsx Encrypts verification code before sending to backend

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

}
setIsLoading(true)
const ret = await webAppEmailLoginWithCode({ email, code, token })
const ret = await webAppEmailLoginWithCode({ email, code: encryptVerificationCode(code), token })
Copy link

Copilot AI Jan 8, 2026

Choose a reason for hiding this comment

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

This change breaks email code login functionality. The frontend now encrypts the verification code using Base64 encoding, but the backend web app email code login endpoint at /email-code-login/validity (in api/controllers/web/login.py) does not have the @decrypt_code_field decorator to decrypt it. The console email code login endpoint uses this decorator, but it's missing for web app login. This will cause all email code login attempts to fail because the backend will compare the Base64-encoded string against the actual code.

Copilot uses AI. Check for mistakes.
const loginData: Record<string, any> = {
email,
password,
password: encryptPassword(password),
Copy link

Copilot AI Jan 8, 2026

Choose a reason for hiding this comment

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

This change breaks web app login functionality. The frontend now encrypts the password using Base64 encoding, but the backend web app login endpoint at /login (in api/controllers/web/login.py) does not have the @decrypt_password_field decorator to decrypt it. The console login endpoint uses this decorator, but it's missing for web app login. This will cause all web app login attempts to fail because the backend will try to authenticate using the Base64-encoded string instead of the actual password.

Copilot uses AI. Check for mistakes.
douxc added a commit that referenced this pull request Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm This PR has been approved by a maintainer size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants