<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5WR00002Q00LM0AZOkta Classic EngineNetwork ZonesAnswered2026-11-10T21:54:56.000Z2026-11-10T04:00:31.000Z2026-11-10T21:54:56.000Z

GlennM.03529 (Customer) asked a question.

TLS 1.3 Firewall allowlist clarification

I've read the KB article posted / updated on October 21:

https://support.okta.com/help/s/article/okta-is-enabling-support-for-tls-1-3-across-okta-services

 

There are some things I'd like clarified from the email and KB guidance:

 

> This migration shifts outbound connectivity from regional endpoints to global public IP addresses across Okta IDaaS TLS, LDAPI, Kerberos, Custom Domains, and mTLS traffic. 

 

...

 

> 2. Update Allowed IP Ranges: Cross-reference your organization's Okta cell with the updated global public IP list.

 

My interpretation of the above is that "Outbound connections from Okta will change from (for example) `apac_cell_1` to a global group of IP addresses.". The document the KB refers to (linked below) does not list a global address cell though.

https://help.okta.com/en-us/content/topics/security/ip-address-allow-listing.htm

 

> If your organization is using Custom Domains and enforces strict firewall allow-lists but does not update them prior to completion of the rollout, your firewall may reject outbound connections to Okta.

 

Is this an exclusive AND? i.e. are outbound connections from `mycompany.okta.com` impacted as well?

 

Ultimately, I'd like to know whether our platforms that have Okta SCIM integration need to update their IP whitelists as a result of this change, and if we're using `apac_cell_1`, what we should change it to.


  • Paul S. (Okta, Inc.)

    Hello @GlennM.03529 (Customer)​ Thank you for posting on our Community page!

     

     

    You are asking whether the Okta TLS 1.3 migration, which moves outbound connections from regional cell addresses to global public IP addresses, requires your SCIM integration allowlists and your default tenant domain (mycompany.okta.com) allowlists to change, and what the apac_cell_1 entry should be replaced with.

     

    Summary: The risk of rejected connections applies when a Custom Domain is combined with a strict firewall allowlist that is not updated, and the exact scope for SCIM and default tenant domain traffic must be confirmed for your tenant through Okta Support before you change allowlists.

     

    Root Cause: The migration changes the source addresses that Okta uses for the listed traffic types (TLS, LDAPI, Kerberos, Custom Domains, and mTLS). Per-cell lists, such as the apac_cell_1 entry in the public IP ranges file, describe the regional addresses and do not contain the global address group. The firewall rejection risk therefore applies only when both conditions are true: your traffic falls under the migrated types, and your firewall rules are not updated before rollout completes.

     

    Solution: Follow these steps:

    1. Open a case with Okta Support that references the TLS 1.3 migration. Ask for the global public IP list and for written confirmation of whether outbound SCIM traffic and default-domain traffic (mycompany.okta.com) are in scope for your tenant.
    2. Review your firewall rules for every SCIM endpoint and every Custom Domain that enforces a strict allowlist. Include all SCIM receiving services in this review.
    3. Add the global addresses from the list Okta Support provides, or, if your firewall supports domain-based rules, add the Okta domains that the community guidance lists (for example, *.okta.com, *.mtls.okta.com, and *.kerberos.okta.com). Domain rules do not depend on IP changes.
    4. Keep the existing apac_cell_1 entries in place until Okta Support confirms that the migration is complete for your cell, then remove them after that confirmation.
    5. Test SCIM provisioning and Custom Domain sign-in from your network after each allowlist change to confirm connections succeed.

     

    Thank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
  • GlennM.03529 (Customer)

    Well, in positive news it looks like human jobs are safe for a little while longer.

Loading
TLS 1.3 Firewall allowlist clarification
Okta Support Agent (Beta)

Terms of Service

Hello! I'm the Okta Support Agent (Beta), your go-to resource for questions about Okta products. Please remember for your security and privacy, do not share any Personally Identifiable Information (PII) such as passwords, IP addresses, or other details with me.

Okta Privacy Policy and Terms of Service apply