Why is IP login restriction (whitelisting) not working for my SaaS application?
A SaaS application may use multiple domain names, and configuring just your personalized domain name may not be enough.
Even though you have configured your SaaS application domain with the name of your company (for example, mycompany.atlassian.com), it may not be enough to configure your SaaS application with that company domain name because common microservices like login may use different domain names (for example, login.atlassian.com).
There are two options to fix this:
- Add all required subdomains as SaaS applications. For example, mycompany.atlassian.com, id.atlassian.com, home.atlassian.com, api.atlassian.com, etc.
- Remove the subdomain and use the domain name to configure your SaaS application. For example, atlassian.com