Use configured external OIDC Provider for 2FA in client #1264
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jun 24, 2025
moubctez
reviewed
Jun 25, 2025
moubctez
reviewed
Jun 25, 2025
moubctez
reviewed
Jun 25, 2025
moubctez
reviewed
Jun 25, 2025
wojcik91
approved these changes
Jun 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds the ability to perform 2FA with the configured OIDC Provider in the client before establishing a VPN connection.
Implements another MFA method "OIDC". Now, a client MFA session can be authorized by authenticating to the configured provider via the proxy.
resolves #1046
Related:
DefGuard/proxy#119
DefGuard/client#467
DefGuard/proto#36