feat(auth): update AUTO_LOGIN authentication to enforce API key or JWT requirement

[ogabrielluiz]

Summary by CodeRabbit

• New Features
  • Enforced stricter authentication: valid API key or JWT is now always required for login, with clearer error handling.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The Memory Chatbot component was refactored to separate sender filtering into sender type and explicit sender inputs, and its outputs were expanded to include both formatted text and DataFrame representations of messages. Authentication logic was updated to enforce stricter API key or JWT requirements, removing fallback behaviors and deprecation warnings.

Changes

File(s)	Change Summary
src/backend/base/langflow/initial_setup/starter_projects/Memory Chatbot.json	Refactored Memory component: split sender filtering into sender_type and sender inputs, added new method for text output (retrieve_messages_as_text), updated output logic to provide both text and DataFrame outputs, adjusted input defaults and visibility, and updated output declarations and internal method logic.
src/backend/base/langflow/services/auth/utils.py	Removed deprecation warnings and fallback logic in authentication; now enforces valid API key or JWT for both HTTP and WebSocket authentication, raising errors when missing, and simplified control flow.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant MemoryComponent

    User->>MemoryComponent: Store message (with sender_type, sender, message)
    MemoryComponent->>MemoryComponent: store_message()
    MemoryComponent-->>User: Confirmation (Message)

    User->>MemoryComponent: Retrieve messages (with sender_type, sender)
    alt Retrieve as text
        MemoryComponent->>MemoryComponent: retrieve_messages_as_text()
        MemoryComponent-->>User: Formatted Message (text)
    else Retrieve as DataFrame
        MemoryComponent->>MemoryComponent: retrieve_messages_dataframe()
        MemoryComponent-->>User: DataFrame
    end

Loading

sequenceDiagram
    participant Client
    participant AuthUtils

    Client->>AuthUtils: Request (API key/JWT missing or invalid)
    alt AUTO_LOGIN enabled
        AuthUtils-->>Client: Error (HTTP 403 or WebSocket policy violation)
    else Valid API key/JWT
        AuthUtils->>AuthUtils: check_key()
        AuthUtils-->>Client: Proceed
    end

Loading

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch fix-1.5-warning

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 auto-generate unit tests to generate unit tests for 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.

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.

[coderabbitai]

Actionable comments posted: 2

🔭 Outside diff range comments (1)

src/backend/base/langflow/services/auth/utils.py (1)

42-44: ⚠️ Potential issue

Runtime NameError risk from ApiKey in local variable annotation

ApiKey is imported only under TYPE_CHECKING, hence it is undefined at runtime.
Local-scope annotations are evaluated when the function executes (PEP 526), so the line

result: ApiKey | User | None

will raise NameError on the very first request that hits api_key_security.

Suggested fix – either import ApiKey unconditionally or avoid the annotation entirely:

-        result: ApiKey | User | None
+        # Only the user instance is returned by `check_key`
+        result: User | None

Alternatively, quote the type ("ApiKey") but that annotation is misleading because check_key returns the related User.

🧹 Nitpick comments (1)

src/backend/base/langflow/services/auth/utils.py (1)

97-105: Duplicate policy-violation block – extract constant / align wording

The WebSocket branch duplicates the exact validation/error wording introduced for HTTP (lines 52-60). Consider:

POLICY_MSG_REQUIRE_KEY = (
    "Since v1.5, AUTO_LOGIN requires a valid API key."
    " Please update your authentication method."
)

and reuse it in both places to keep wording in sync and avoid future drift.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ab1ed8e and e87df0f.

📒 Files selected for processing (2)

• src/backend/base/langflow/initial_setup/starter_projects/Memory Chatbot.json (4 hunks)
• src/backend/base/langflow/services/auth/utils.py (2 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

src/backend/base/langflow/services/auth/utils.py (2)

src/backend/base/langflow/services/database/models/api_key/crud.py (1)

• check_key (52-61)

src/backend/base/langflow/__main__.py (1)

• api_key (568-615)

🔇 Additional comments (2)

src/backend/base/langflow/initial_setup/starter_projects/Memory Chatbot.json (2)

856-866: Approve addition of text output mapping.

The new messages_text output is correctly configured to use retrieve_messages_as_text, providing the formatted message history as a Message object. Method exists and aligns with the updated component API.

---

868-870: Approve DataFrame output mapping.

The dataframe output now correctly calls retrieve_messages_dataframe, returning messages as a DataFrame. Configuration matches the component definition.

[coderabbitai]

🛠️ Refactor suggestion

Error message promises JWT support that this branch cannot fulfil

The new 403 block states “AUTO_LOGIN requires a valid API key or JWT.” but immediately afterwards you call check_key, which can validate API keys only. Supplying a JWT through x-api-key will still trigger the Invalid or missing API key path.

Either:

1. Change the message to mention API keys only, or
2. Add JWT detection here (e.g. delegate to get_current_user_by_jwt when the token looks like a JWT).

Keeping the message as-is will confuse users and support teams.

🤖 Prompt for AI Agents

In src/backend/base/langflow/services/auth/utils.py around lines 52 to 60, the
error message incorrectly states that AUTO_LOGIN requires a valid API key or
JWT, but the code only validates API keys via check_key. To fix this, either
update the error message to mention only API keys or enhance the logic to detect
JWT tokens and delegate validation to get_current_user_by_jwt when a JWT is
supplied, ensuring the message matches the actual validation performed.

[jordanrfrazier]

Should we include LANGFLOW_ prefix? LANGFLOW_AUTO_LOGIN?

[ogabrielluiz]

Yes.

[jordanrfrazier]

.

[jordanrfrazier]

since this is True by default, isn't the behavior unchanged (i.e. it's the same as pre-v1.5 behavior)?