This repository has been archived by the owner on Feb 15, 2024. It is now read-only.
Add support for limiting source IPs that can submit disable request payloads #18
Comments
atc0005
added a commit
that referenced
this issue
Nov 10, 2020
Check remote IP Address against a list of user-provided or default IP Addresses. If not match is found, reject the connection with forbidden status. Update docs, config template to reflect the changes. refs GH-18
atc0005
added a commit
that referenced
this issue
Nov 10, 2020
Check remote IP Address against a list of user-provided or default IP Addresses. If a match is not found, reject the connection with forbidden status. Update docs, config template to reflect the changes. refs GH-18
atc0005
added a commit
that referenced
this issue
Nov 10, 2020
Check remote IP Address against a list of user-provided or default IP Addresses. If a match is not found, reject the connection with forbidden status. If a match is found, accept the connection. If the sysadmin does not provide a list of trusted IP Addresses via config file or CLI flag, accept payloads from any IP Address. An attempt to balance this choice is provided by setting the default value in the starter config file to 127.0.0.1, or "localhost". This behavior is subject to change; the behavior may change to require an explicit list of IP Addresses to receive payloads. Update docs, config template to reflect the changes. refs GH-18
atc0005
added a commit
that referenced
this issue
Nov 10, 2020
Check remote IP Address against a list of user-provided or default IP Addresses. If a match is not found, reject the connection with forbidden status. If a match is found, accept the connection. If the sysadmin does not provide a list of trusted IP Addresses via config file or CLI flag, accept payloads from any IP Address. An attempt to balance this choice is provided by setting the default value in the starter config file to 127.0.0.1, or "localhost". This behavior is subject to change; the behavior may change to require an explicit list of IP Addresses to receive payloads. Update docs, config template to reflect the changes. refs GH-18
atc0005
added a commit
that referenced
this issue
Nov 10, 2020
Check remote IP Address against a list of user-provided or default IP Addresses. If a match is not found, reject the connection with forbidden status. If a match is found, accept the connection. If the sysadmin does not provide a list of trusted IP Addresses via config file or CLI flag, accept payloads from any IP Address. An attempt to balance this choice is provided by setting the default value in the starter config file to 127.0.0.1, or "localhost". This behavior is subject to change; the behavior may change to require an explicit list of IP Addresses to receive payloads. Update docs, config template to reflect the changes. refs GH-18
atc0005
added a commit
that referenced
this issue
Nov 10, 2020
Check remote IP Address against a list of user-provided or default IP Addresses. If a match is not found, reject the connection with forbidden status. If a match is found, accept the connection. If the sysadmin does not provide a list of trusted IP Addresses via config file or CLI flag, accept payloads from any IP Address. An attempt to balance this choice is provided by setting the default value in the starter config file to 127.0.0.1, or "localhost". This behavior is subject to change; the behavior may change to require an explicit list of IP Addresses to receive payloads. Update docs, config template to reflect the changes. refs GH-18
atc0005
added a commit
that referenced
this issue
Nov 11, 2020
If provided, check remote IP Address against the list of user-provided IP Addresses. If a match is not found, reject the connection with forbidden status. If a match is found, accept the connection. If the sysadmin does not provide a list of trusted IP Addresses via config file or CLI flag, accept payloads from any IP Address. An attempt to balance this choice is provided by setting the default value in the starter config file to 127.0.0.1, or "localhost". This behavior is subject to change; the behavior may change to require an explicit list of IP Addresses to receive payloads. Update docs, config template to reflect the changes. refs GH-18
atc0005
added a commit
that referenced
this issue
Nov 11, 2020
If provided, check remote IP Address against the list of user-provided IP Addresses. If a match is not found, reject the connection with forbidden status. If a match is found, accept the connection. If the sysadmin does not provide a list of trusted IP Addresses via config file or CLI flag, accept payloads from any IP Address. An attempt to balance this choice is provided by setting the default value in the starter config file to 127.0.0.1, or "localhost". This behavior is subject to change; the behavior may change to require an explicit list of IP Addresses to receive payloads. Update docs, config template to reflect the changes. refs GH-18
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This would help limit abuse of the API by only allowing specified IPs.
For our use case this would include a trusted Splunk search head, sysadmin/developer workstation IPs.
The text was updated successfully, but these errors were encountered: