[FEATURE] Authentication

[Jarnster]

Is your feature request related to a problem? Please describe.
Authentication should be implemented on the backend API and frontend.

Describe the solution you'd like

• OIDC integrations using ENV values
• User permission groups
• Audit logging

Update: Advanced authentication (RBAC, audit, OIDC) won't be possible in this current codebase.
In the meanwhile we'll implement a simple authentication feature like described in #62 (comment) and #43 (comment)

[zarlo]

having oidc as an option would be nice, it could use the users clams to map to permission groups

[mrpops2ko]

honestly theres so much off the shelf stuff that will do a much better job of security (authentik, authelia etc) that i wonder why bother

stick it in a docker container in its own private network that is only accessible via reverse proxy with one of those off the shelf security front doors

[Jarnster]

honestly theres so much off the shelf stuff that will do a much better job of security (authentik, authelia etc) that i wonder why bother

stick it in a docker container in its own private network that is only accessible via reverse proxy with one of those off the shelf security front doors

Depending on how long it takes for our rewrite: we'll probably just add that as a quick simple alternative. We're spending a lot of time at the rewrite we will still decide if we make this change for the time until we publish the rewrite. You can always make a PR.

Currently we're rewriting a lot regarding the access layer to VyOS routers, like you may have been able to see in our Discord server. Eventually we will also work towards a better approach regarding authentication and frontend.