From bf8ac287d7d1366df7a8a8f9748e349f9d2046b7 Mon Sep 17 00:00:00 2001
From: ChainSauz <22598783+ChainSauz@users.noreply.github.com>
Date: Sat, 9 Nov 2024 00:41:48 -0500
Subject: [PATCH] Update opnsense.md to reflect effective privileges section

Amend notes on effective privileges that need to be selected for OPNSense API. It appears that in the 24.7.x release the "Status: Traffic Graph" privilege no longer exists. However, this appears to have been replaced / is covered by the Reporting: Traffic privilege grouping, which covers the /api/diagnostics/traffic/* endpoint(s).
---
 docs/widgets/services/opnsense.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/widgets/services/opnsense.md b/docs/widgets/services/opnsense.md
index ddda62ff..faaba6b8 100644
--- a/docs/widgets/services/opnsense.md
+++ b/docs/widgets/services/opnsense.md
@@ -8,7 +8,7 @@ Learn more about [OPNSense](https://opnsense.org/).
 The API key & secret can be generated via the webui by creating a new user at _System/Access/Users_. Ensure "Generate a scrambled password to prevent local database logins for this user" is checked and then edit the effective privileges selecting **only**:
 
 - Diagnostics: System Activity
-- Status: Traffic Graph
+- Status: Traffic Graph / Reporting: Traffic (OPNSENSE 24.7.x)
 
 Finally, create a new API key which will download an `apikey.txt` file with your key and secret in it. Use the values as the username and password fields, respectively, in your homepage config.