Changes with IP Addresses Used tenantname.api.identitynow.com/oauth/token?

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Since around April of this year our non-web facing servers have been unable to login to SailPoint via the API call in the title. This is causing us quite a few issues with 3rd Qtr security reviews. Any web facing server works fine but I really don’t want to just open these servers up to the web.

Does anyone know what was changed? I’m assuming something with the move to V3? Ideally I’d like to just whitelist a group of IPs but I’m not sure if that will be feasible given these are likely a wide range of AWS addresses. I’m more concerned as to what changed that all of a sudden in April this would become an issue.

2

Hello @crderosier,

Depending on where your tenant is located, there is a handful of IPs that can be whitelisted, but these do cycle. Here is a great article regarding this: IP Address Allow List | SailPoint Developer Community

I hope this helps :slight_smile:

3

Thanks @bcariaga. We actually did try whitelisting port 443 for those IP addresses for our tenant but that didn’t help unfortunately. I noticed the IP addresses that are getting blocked also aren’t on the list for our tenant at all. Here’s some examples

18.210.130.9
50.16.16.133

Those two show up a ton and appear to be AWS servers.

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.