Any chance the whitelist for API (or frankly all whitelists) could be made to support (or currently support?) subnet masks? For example, if I have a dynamic pool of IPs that could hit but are all on the same Class C network, it would be great to do something like:
35.203.252.0/24
and have that work for any address coming from the 35.203.252.* address space. With our serverless app approach, having to designate specific IPs is of no use as the address coming from a Class B space, i.e., 255x255 possibilities.
API Whitelist Mask
-
Kent Briggs
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: API Whitelist Mask
The * wildcard mask is already supported. From the help file:
API whitelist - Specify a list of IP addresses (one per line) that can access the API commands. This is a security feature that can prevent unauthorized access to your game server even if the API password becomes compromised. Leave this setting blank to allow access from any IP address. You may include asterisks as octet/hextet wildcards in IPv4/IPv6 addresses (examples: 192.168.1.*, 1234
123412341234:*).
API whitelist - Specify a list of IP addresses (one per line) that can access the API commands. This is a security feature that can prevent unauthorized access to your game server even if the API password becomes compromised. Leave this setting blank to allow access from any IP address. You may include asterisks as octet/hextet wildcards in IPv4/IPv6 addresses (examples: 192.168.1.*, 1234
123412341234:*).