feat: add extensible auth field monitor for automatic logout

[nick-y-snyk]

Summary

Implements extensible infrastructure to automatically trigger logout when authentication-sensitive fields change, using the dirty tracker's change listener pattern.

Changes

• Dirty Tracker: Added extensible change listener system (addChangeListener, _notifyChangeListeners)
• Auth Field Monitor: New module that monitors endpoint and authenticationMethod fields
• Integration: Register monitor as change listener during app initialization
• Cleanup: Removed previous endpoint tracking from auto-save and duplicate validation listener

Architecture

The dirty tracker now fires callbacks to registered listeners on every data change, passing both original and current data. This allows monitors to implement custom logic without coupling to the tracker.

Extensibility

New monitors can be added by:

window.dirtyTracker.addChangeListener(function(originalData, currentData) {
    // Custom logic here
});

Or extend existing monitors:

window.ConfigApp.authFieldMonitor.addAuthSensitiveField('newField');

Test plan

• Change endpoint field and verify logout is triggered
• Change authenticationMethod field and verify logout is triggered
• Change other fields and verify logout is NOT triggered
• Verify auto-save still works correctly
• Verify dirty state tracking still works correctly

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @nick-y-snyk, 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 a robust and extensible mechanism to enhance security by automatically logging out users when critical authentication-related configuration fields are modified. By integrating with the existing dirty tracker, the system now provides a centralized way to monitor data changes and react to them, ensuring that any alterations to sensitive authentication settings prompt a necessary re-authentication. This design improves maintainability and allows for easy addition of new fields to monitor in the future.

Highlights

• Extensible Dirty Tracker: The dirty tracker now includes an extensible change listener system, allowing external modules to register callbacks that are invoked whenever data changes.
• Auth Field Monitor Module: A new module, AuthFieldMonitor, has been introduced to specifically monitor changes to authentication-sensitive fields such as endpoint and authenticationMethod.
• Automatic Logout Integration: The AuthFieldMonitor is registered as a change listener during application initialization. If it detects a change in an authentication-sensitive field, it automatically triggers a user logout.
• Code Cleanup and Refactoring: Previous ad-hoc logic for endpoint tracking in the auto-save feature and duplicate validation listeners for authentication method changes have been removed, streamlining the codebase.

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

[gemini-code-assist]

Code Review

This pull request introduces a well-designed, extensible mechanism for automatically logging out the user when authentication-sensitive fields are changed. The new change listener pattern in the dirtyTracker is a solid foundation for this and other features. The code is clean, and the refactoring to remove the old endpoint tracking logic is a good improvement. My main review point concerns the authFieldMonitor module, which doesn't fully implement the extensibility described in the pull request summary. I've provided a detailed comment with a code suggestion to align the implementation with the stated design goals.