-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/dhv3 #138
Feature/dhv3 #138
Conversation
This routes /url/authenticate requests from the Cisco Umbrella CIDRs to a different page. This prevents Cisco from 'logging in' and preventing the user from logging in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice if cidrs could be added through the config
You can now add `blockCidrs` to the client config. Example: ``` { "blockCidrs": [ "1.2.3.4/16", "4.4.4.4/16" ] } ``` When the `blockCidrs` key does not exist in the client config, the block cidrs default to the Cisco umbrella CIDRs. Note: This means that if you want to add CIDRs to the block CIDRs, and you want to keep the Cisco Umbrello CIDRs, you have to add those to the client config as well.
Agreed, I've added this, with instructions in the readme. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice :)
Description
Add CIDR-based blocker to prevent e-mail filters (e.g. Cisco Umbrella) from invalidating a login link
Type of change
New feature
Tests
Manually