Skip to content

Add default instance auto-connect on startup#826

Draft
Faerbit wants to merge 1 commit intoDefGuard:devfrom
Faerbit:feat/default-instance-auto-connect
Draft

Add default instance auto-connect on startup#826
Faerbit wants to merge 1 commit intoDefGuard:devfrom
Faerbit:feat/default-instance-auto-connect

Conversation

@Faerbit
Copy link
Copy Markdown

@Faerbit Faerbit commented Apr 25, 2026

📝 New contributors

  • I have read, understand, and agree to the Contributor Agreement. By checking this box, I confirm I have the right to contribute this work and I grant Defguard sp. z o.o. the necessary rights to use my contribution as outlined in the full agreement.: https://tnt.sh/s/defguard-contribution-agreement

⚠︎ If the checkbox will not be confirmed - we can't include your contribution in our codebase.

📖 Description

Add default instance auto-connect on startup

Adds a settings dropdown to configure which instance should be automatically connected when the client launches. A companion checkbox enables triggering MFA prompts during auto-connect for locations that require it (disabled by default). Selecting "None" (the default) preserves the existing behaviour of no auto-connect.

Relates to #606. Doesn't necessarily close it, as it only connects to one instance.

🛠️ Dev Branch Merge Checklist:

Documentation

  • If testing requires changes in the environment or deployment, please update the documentation (https://docs.defguard.net) first and attach the link to the documentation section in this pull request
  • I have commented on my code, particularly in hard-to-understand areas

Docs: #62

Testing

  • I have performed manual tests manually and all changes work
  • New and existing unit tests pass locally with my changes

I was able to successfully test my changes on the main branch. I rebased the changes to the dev branch, because I assume this is the preferred development workflow. I'm unable to verify my changes on the dev branch, because it currently doesn't build.

🏚️ Main Branch Merge Checklist:

Testing

  • I have merged my changes before to dev and the dev checklist is done
  • I have tested all functionalities on the dev instance and they work

Documentation

  • I have made corresponding changes to the user & admin documentation and added new features documentation with screenshots for users/admins

@Faerbit Faerbit marked this pull request as draft April 25, 2026 16:49
@Faerbit Faerbit force-pushed the feat/default-instance-auto-connect branch 2 times, most recently from 0c1dff1 to c7d4286 Compare April 25, 2026 16:55
Adds a settings dropdown to configure which instance should be
automatically connected when the client launches. A companion checkbox
enables triggering MFA prompts during auto-connect for locations that
require it (disabled by default). Selecting "None" (the default)
preserves the existing behaviour of no auto-connect.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Faerbit Faerbit force-pushed the feat/default-instance-auto-connect branch from c7d4286 to 14b426a Compare April 25, 2026 16:56
@Faerbit Faerbit marked this pull request as ready for review April 25, 2026 17:01
@Faerbit
Copy link
Copy Markdown
Author

Faerbit commented Apr 25, 2026

I would like to agree to your CA, but cannot read it as the link 404s.

@teon
Copy link
Copy Markdown
Contributor

teon commented Apr 27, 2026

Thank you @Faerbit for your contribution 🫡

We are in the middle of 2.0 release and have much workflow - as we would like to release it this week.

Well get back to review this PR after the release!

@Faerbit Faerbit marked this pull request as draft April 27, 2026 21:09
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.

2 participants