[Support]: Authentik Configuration #13329
Replies: 4 comments 1 reply
-
if you want to use frigate's built in authentication then there is no need for a reverse proxy to provide authentication. If you want to use proxy authentication then yes frigate's authentication would be disabled. The configuration of the proxy auth is something that you would find better support elsewhere |
Beta Was this translation helpful? Give feedback.
-
https://docs.frigate.video/configuration/authentication/#proxy-configuration |
Beta Was this translation helpful? Give feedback.
-
Were you able to complete the authentik auth setup with frigate or did you use any other auth proxy? |
Beta Was this translation helpful? Give feedback.
-
So this is specific to my setup but it looks like I was able to make it work this time. Since this is still the top result if I Google Authentik Frigate - I should probably provide some sort of help. I don't know how much of this is necessary as this was frustrating to get working. For this setup I am using Cloudflare tunnels for all access. My Authentik host is accessed through a CF tunnel. The Authentik host is on the same network as the Frigate host and can be accessed with mDNS. FrigateFrigate config changes:
AuthentikIn Authentik make a provider with the following settings: Navigate to Applications -> Outposts Edit the authentik Embedded Outpost and add the provider to the list Create an Application for Frigate and select the provider created previously (no other changes should be necessary). Set up your preferred access rules CloudflareModify the tunnel providing access to your Authentik instance. Add a second hostname for Deploy and that's it. When accessing the frigate external address you will be prompted to login to Authentik. Once logged in you will be transparently passed through to Frigate. All traffic to Frigate will flow through Authentik's proxy. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
Now that Frigate supports auth - does someone have an example configuration on the Authentik side to auth with Frigate?
I don't have a reverse proxy or anything in front of frigate right now and only access it locally via mDNS but would like to potentially open it up (which would end up going through a Cloudflare tunnel) and secure it through Authentik.
Is a reverse proxy required?
I've tried a few combinations with the Authentik proxy but can't find something that passes headers appropriately. Just setting auth to disabled (as shown in the attached config) allows anyone in with no authentication whatsoever so that's not ideal.
Version
14.0
What browser(s) are you using?
No response
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
No response
Operating system
Proxmox
Install method
Docker Compose
Object Detector
Coral
Network connection
Wired
Camera make and model
Multiple
Screenshots of the Frigate UI's System metrics pages
No response
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions