In this video, I demonstrate setting up email and webhook notifications for Authentik events. Documentation Resources: Notifications - goauthentik.io/docs/events/no... Transports - goauthentik.io/docs/events/tr...
Glad to hear that! When I was a beginner there weren't any videos...maybe the 1 by ibracorp but that was it. So, I wish I had these videos when I was starting...I'd be much further along; LOL. And the early documentation was not easy to understand especially having no knowledge coming into it... I think the documentation has improved, but the more examples, scenarios, screenshots, and videos there are the better someone can jump right into it.
That's a great video. In fact all of your Authentik tutorials are extreamly helpful! Could you consider creating a video explaining how to ban an IP from trying to authenticate if their reputation gets too low? Or Crowdsec integration?
...not sure what you mean...however, if you mean will you get notified if any users or admins login, logout, fail...yes, you will because it is by event (policies will help you customize it more if needed)
Your video was informative but can you elaborate more on the email setup or create a short video covering that part? I have email configured globally and i test that its working using the step provided from authentik email troubleshooting docs. However, after following your guide i still can't get notification of login events. Not sure what i am missing. Do i need to create an email stage outside the default one?
I generally make specific stages and try not to mess with the default ones when possible...that said, your default settings should work if email is working. The default email stage utilize the templates (recovery/invite), the notification setup uses its own so long as emails are working.
Amazing video series. You helped me fully setup my authentik! Is there a way to bypass auth altogether with apps behind authentik if on a local network?
Thank you! That was my intention for the videos...to simply get set up, and from there depends on the users' needs. See my other video here regarding bypass of auth on LAN: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-c2_C9VOgGZI.html
That is a tough one...I think you still, at minimum, need a user login to load proper groups/permissions... Maybe, just maybe a policy can be applied that check if the user exists AND is being access from the LAN, if so, bypass the password stage.
...most issues when it comes to using gmail as a relay is trying to use the main account password. So be sure you are creating an application password and using that. Also that you have an alias that can be used as your "send as". If all that fails, manually enter the settings in your email flow to see if that works. (also be sure the email environment variables are in both your server and worker)
