DefGuard/defguard

[Design]: Add possibility to make client traffic settings location/group-based

Open

#2,820 opened on Apr 27, 2026

View on GitHub
 (1 comment) (1 reaction) (1 assignee)Rust (107 forks)auto 404
featurehelp wanted

Repository metrics

Stars
 (2,779 stars)
PR merge metrics
 (PR metrics pending)

Description

Problem description

"Client Configuration Permissions" and "Client traffic policy" shouldn't be a product wide setting. We want to allow certain users to create manual WireGuard configurations or allow some users to allow all traffic.

Proposed solution

Make "Client Configuration Permissions" and "Client traffic policy" a user/group-based setting.

Alternatives considered

No response

Impact

Important

Contributor guide

Research direction
Examine the current implementation of 'Client Configuration Permissions' and 'Client traffic policy' in the codebase to understand where and how these settings are stored and applied. Then design a multi tenancy model that associates these settings with user groups instead of being product wide.
Tech stack
rust
Domain
securityauthorizationnetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50