Project

General

Profile

Feature #6176

Privilege for OpenVPN Client Export

Added by Alexandre Paradis over 3 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
OpenVPN Client Export
Target version:
-
Start date:
04/15/2016
Due date:
% Done:

0%

Estimated time:

Description

Hello pfsense dev,

When creating a custom group with only "WebCfg - OpenVPN: Client Export Utility" , there is no dropdown menu in the top taskbar to click OpenVPN.

I have access with the direct link : https://example.com/vpn_openvpn_export.php

If I want to have the Openvpn menu to have access to the export utility, i need to also add the server page "WebCfg - OpenVPN: Server".

Would it be logical to Have a dropdown menu directly for Openvpn, and when clicked it would redirect to the export utility page ?

Also, last thing ... Would it be possible to create another filter with only the "OpenVPN Clients" in the "WebCfg - OpenVPN: Client Export Utility" ?

something like "WebCfg - OpenVPN: Client Export Utility: OpenVPN Client"

Thanks in advance!

History

#1 Updated by Chris Buechler over 3 years ago

  • Tracker changed from Bug to Feature
  • Project changed from pfSense to pfSense Packages
  • Subject changed from custom user group - openvpn client export utility issue to Privilege for OpenVPN Client Export
  • Category changed from Web Interface to OpenVPN Client Export
  • Affected Architecture deleted (All)

#2 Updated by bearsh bearsh about 3 years ago

it would be very cool to be able to limit access for users to their own client configs. users don't need to have access to the configs of other users...

#3 Updated by Kill Bill over 2 years ago

Alexandre Paradis wrote:

Would it be logical to Have a dropdown menu directly for Openvpn, and when clicked it would redirect to the export utility page ?

Where? In the VPN menu?

Also, last thing ... Would it be possible to create another filter with only the "OpenVPN Clients" in the "WebCfg - OpenVPN: Client Export Utility" ?

Nope, not without spliting that part of the page into a separate PHP file, plus that wouldn't really make much sense without being able to configure the rest of the export aspects.

bearsh bearsh wrote:

it would be very cool to be able to limit access for users to their own client configs. users don't need to have access to the configs of other users...

Uhm. No, not without huge hassle with pfSense user vs. certificate/VPN user mapping.

Also available in: Atom PDF