You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using an Identity Provider in front of my webserver. This is handy and I can exclude regex patterns of the URL from 2FA to let webhook and api calls pass without 2FA.
As an example>
With a regex filter like:
.(/)?/BANANA-.
All bots are being blocked and will never reach one of my backend servers. Expect they know the pattern. In addition there is fail2ban in place and a strong firewall in front to block bruteforce in addition.
This is already in place with Home Assistant + Authentik
Would be nice if it would be possible to adjust the URL
Best regards,
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Somewhat a problem for me but maybe for others as I am not able to adjust the ingres webhook URL.
Describe the solution you'd like
Create a custom webhook with encrypted code but let us change it as desired.
If the created webhook is: https://domain.com/ingest/i5alQYCayb6mPSMc let me adjust it to whatever I like after https://domain.com/ingest/
Describe alternatives you've considered
None
Additional context
I am using an Identity Provider in front of my webserver. This is handy and I can exclude regex patterns of the URL from 2FA to let webhook and api calls pass without 2FA.
As an example>
With a regex filter like:
.(/)?/BANANA-.
I can force authentication on
https://domain.com/whatever
but bypass 2FA on
https://domain.com/BANANA-asda2dsdasd
All bots are being blocked and will never reach one of my backend servers. Expect they know the pattern. In addition there is fail2ban in place and a strong firewall in front to block bruteforce in addition.
This is already in place with Home Assistant + Authentik
Would be nice if it would be possible to adjust the URL
Best regards,
The text was updated successfully, but these errors were encountered: