IP whitelisting

[alula]

This has been requested multiple times on feedback.discordapp.com, and since you are improving developer's experience and nobody opened an issue for that... I've just opened one :^)

IP whitelisting is another must-have thing in teams, because there's higher chance to accidentally leak secrets (even by misconfiguration, bigger projects are at higher risk). Whitelisting of ipv4/ipv6 addresses and ranges (eg. /24) for API requests and gateway connection should be enough for now.

[Lachee]

Similar to issue #644

[TheRockettek]

You could also just like not leak your token :^)

[xJade00]

@TheRockettek I suppose you're just automatically immune to people who work on your bot with you leaking the token on purpose for any number of reasons?

There are plenty of valid reasons to want this ability to whitelist.

[TheRockettek]

So it would seem

[alula]

I actually never leaked my token, but additional layer of security is always good. Also what if my co-worker misconfigures something and app secrets get leaked? Human mistakes are really common.

[Lachee]

@TheRockettek this is a honest suggestions. Its a basic security feature that is widely used in the industry. A notable example i know off is EVE Online which require it for their oAuth implementation.

Not leaking your token is the first step of security, just like how 2FA is another. This IP whitelist would just be an extra layer of additional security for those larger bots that want to be absolutely sure they are safe. Issue #644 actually built upon this idea and suggested a way to find the ips running the token.

As for implementation, this would need to be an array of IP addresses. I dont think a simple /24 range would be suitable and having something like the redirect_uri in oauth applications would be better. A limited number of fixed IP addresses that you know for sure the bot will be running on. Multiple would be required for things such as Lavalink nodes and load balancing.

[Mehgugs]

What is going to stop people leaking your token and also whitelisting their IP address(es).

[trinitrotoluene]

You can unintentionally leak your token, but it's hard to unintentionally whitelist malicious IP addresses without someone having compromised your account...

[Lachee]

@Mehgugs 2FA

[LingleDev]

It would be nice if Discord would implement an IP whitelist for secrets and tokens so only whitelisted IP addresses could connect to the gateway or get a user's access token with a leaked credential.

[HPaulson]

This is a very very nice feature. Maybe it could even be optional? This would give much much more sense of security to larger bots, and "dont leak your token" isn't a very valid argument, considering, you could say the same about 2FA. "Just dont leak your password and email", but we still all use 2FA, as it's a good practice to keep us secure.