OpenSource/homepage
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added instructions on how to restrict Omada User privileges for widget

Browse Source
This commit is contained in:
Jannik Heym 2024-08-14 16:41:30 +02:00 committed by GitHub
parent 2ee14eb94b
commit ea01c273de
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/widgets/services/omada.md
View File

@ -5,6 +5,19 @@ description: Omada Widget Configuration
The widget supports controller versions 3, 4 and 5. The widget supports controller versions 3, 4 and 5.
In order to restrict the user for API access to the bare minimum, one has to follow these steps:
1. Change organization to `Global View`
2. Go to `Account` settings in the lower left corner
3. Navigate to `Role` in the upper bar and add a new Role with the following priviliges
1. Site - `Dashboard Manager` to `View only`
2. Site - `Log Manager` to `View only`
4. Choose a name of your liking
5. Go back to `User` in the upper bar and create a new user for your homepage with the just created Role
6. Select the sites, this API User should have access to
Now you can use the `username` and `password` of this User, having only the required privileges for all allowed fields.
Allowed fields: `["connectedAp", "activeUser", "alerts", "connectedGateways", "connectedSwitches"]`. Allowed fields: `["connectedAp", "activeUser", "alerts", "connectedGateways", "connectedSwitches"]`.
```yaml ```yaml