Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Granular Kea Privileges Not Allocating #8388

Open
CanisVY opened this issue Mar 1, 2025 · 1 comment
Open

Granular Kea Privileges Not Allocating #8388

CanisVY opened this issue Mar 1, 2025 · 1 comment
Labels
support Community support

Comments

@CanisVY
Copy link

CanisVY commented Mar 1, 2025

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

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

Unable to grant granular access to KEA Services subcategories.
page-dhcp-kea-v4 matches include:
ui/kea/dhcp/v4
api/kea/dhcpv4/*
api/kea/leases4/*
api/kea/service/*

I would expect these permissions to grant access to all Kea subcategories including Control Agent, Leases DHCPv4, and Log File.

When granting a group access to this privilege ID, the user is only able to see Kea DHCP4

Image

have the user in question directly navigate to
/ui/kea/dhcp/leases4
/ui/diagnostics/log/core/kea
/ui/kea/dhcp/ctrl_agent
redirects the user to the Lobby

Describe the solution you like

The ability to provide more granular access to kea subpages by means of direct permissions and assignment of page-dhcp-kea-v4 granting access to only the kea services section.

Describe alternatives you considered

granting id page-all

Additional context

I am using OPNSense as a learning tool for an aspiring cybersecurity professional, thank you for your work!

@fichtner fichtner added the support Community support label Mar 2, 2025
@fichtner
Copy link
Member

fichtner commented Mar 2, 2025

ACL files are pluggable, so you can add any combination you like. For maintenance reasons we don't make the ACLs too fine grained as keeping them in sync is tricky as code changes and new features are added (and old ones removed). The static page ACLs also suffered from being too fine grained, especially because their use was driven by the page name and functionality and how it was included in the parent page.

Cheers,
Franco

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

2 participants