Add Memgraph authentication support

[qdrddr]

• Add MEMGRAPH_USERNAME and MEMGRAPH_PASSWORD environment variables
• Update MemgraphIngestor to accept optional username/password parameters
• Pass credentials to all Memgraph connections throughout the codebase
• Update configuration files to support authenticated connections

[gemini-code-assist]

Summary of Changes

Hello @qdrddr, I'm Gemini Code Assist¹! 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 introduces comprehensive support for Memgraph database authentication. It enables users to secure their Memgraph connections by providing a username and password via environment variables. The changes propagate these credentials through the application's configuration and ensure that all interactions with the Memgraph database are made using the specified authentication details, thereby enhancing the overall security posture of the application.

Highlights

• Memgraph Authentication Environment Variables: New environment variables, MEMGRAPH_USERNAME and MEMGRAPH_PASSWORD, have been introduced in .env.example and added to the AppConfig for specifying Memgraph connection credentials.
• MemgraphIngestor Update: The MemgraphIngestor class now accepts optional username and password parameters in its constructor, allowing for authenticated connections to the Memgraph database.
• Credential Propagation: Memgraph connection points throughout the codebase (e.g., main.py, mcp/server.py, realtime_updater.py) have been updated to pass the newly configured MEMGRAPH_USERNAME and MEMGRAPH_PASSWORD to the MemgraphIngestor.
• Secure Connection Establishment: The MemgraphIngestor's __enter__ method now utilizes the provided username and password when establishing the mgclient.connect session, enabling secure authenticated connections.

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. ↩

[gemini-code-assist]

Code Review

This pull request adds authentication support for Memgraph, which is a great enhancement. The implementation is mostly correct, but there's a critical issue: the mgclient.connect function expects a user parameter, but username is used instead throughout the codebase. This will cause authentication to fail. I've left comments in all affected files to correct this, suggesting a rename of the parameter and related configuration variables to user for consistency. I've also suggested adding validation to ensure that if a password is provided, a user is also provided.

[vitali87]

Good feature addition. One inconsistency to address:

The .env.example comment states:

"If authentication is enabled, provide both username and password"

But the code allows username without password:

if self._username:
    connect_params["username"] = self._username
    connect_params["password"] = self._password if self._password else ""  # allows empty

Meanwhile, password without username raises an error.

Please either:

1. Add validation to require both when either is provided, OR
2. Update the comment to indicate password is optional

[vitali87]

Good feature addition. One inconsistency to address:

The .env.example comment states:

"If authentication is enabled, provide both username and password"

But the code allows username without password:

if self._username:
    connect_params["username"] = self._username
    connect_params["password"] = self._password if self._password else ""  # allows empty

Meanwhile, password without username raises an error.

Please either:

1. Add validation to require both when either is provided, OR
2. Update the comment to indicate password is optional

Superseded by request-changes review

[vitali87]

@qdrddr please address the comments above

[qdrddr]

@vitali87 the memgraph auth, if enabled require both username & password to be set.
Fixed in codebase_rag/services/graph_service.py

[vitali87]

Thanks for the update!

This PR is cleaner than the others - nice work on the validation logic.

Just a few adjustments needed to align with CONTRIBUTING.md:

• Remove inline comments (or prefix with (H) if truly necessary)
• Rebase on latest main
• Install pre-commit hooks: pre-commit install

Alternatively, I can make these adjustments myself and merge with attribution to you.

Let me know!