Skip to content

2FA - Use configured external OIDC Provider for 2FA #1046

@Zappo-II

Description

@Zappo-II

Is your feature request related to a problem? Please describe.

Not as such. At least not a Functional / Technical Problem with DefGuard but an Organisational Problem we see with running 2FA in our context using DefGuard.

Describe the solution you'd like

We use Authentik as an OpenIDConnect Provider and have 2FA in Place there. It is exposed to the Internet since we have both types of Applications running, exposed to the Internet and VPN internal. Evaluating DefGuard we thought that the 2FA for Wireguard would be an additional "Login" to the configured external OIDC via DefGuard Client. But instead, DefGuard just adds another TOTP to the game which is puzzling for the EndUser at least...

Describe alternatives you've considered

None with DefGuard, there are several alternatives that introduce a 2FA Approach with Additional TOTPs but that's not what we where hoping to find.

Additional context

We like OpenSource and would like to see this Feature in DefGuard (Enterprise Features) and would consider buying an Enterprise Subscription if that Feature would be met...

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    Ready to release

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions