<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
0D5WR00002MDWTM0A5Okta Classic EngineOkta Integration NetworkAnswered2026-10-30T00:48:35.000Z2026-10-29T02:41:26.000Z2026-10-30T00:48:35.000Z

KeiK.29963 (Customer) asked a question.

Inquiry Regarding Group Linking for the “Zscaler Internet Access” Application Created from the OIN Catalog

We would appreciate your assistance in confirming the behavior of Group Linking for the “Zscaler Internet Access” application created from the OIN Catalog.

​

(1) Question / Request

We have integrated Okta and ZIA using SAML SSO and SCIM provisioning.

However, we are unable to link an Okta group (Name: okta-test2) to an existing group with the same name (okta-test2) that was created directly in the Zscaler administration console, using Push Groups in Okta.

Specifically, when attempting to link the group, the message “No matches found” is displayed and the ZIA group does not appear as a selectable option.

 

Could you please advise on the possible cause of this issue?

Thank you in advance for your assistance

 

(2) Investigation / Troubleshooting Performed

  • We have also confirmed that the OIN integration supports Group Linking.
  • Single Sign-On is working without any issues.
  • Provisioning is functioning properly except for Group Linking. We have confirmed that the following operations work as expected:
  1. User creation
  2. User attribute updates
  3. User deactivation
  4. Pushing groups to ZIA (synchronizing groups created in Okta to ZIA)

 

  • We performed the following steps to verify Group Linking:
  1. Navigated to Applications > Zscaler Internet Access > Push Groups and selected Refresh Application Groups.
  2. Selected Link Group for the target Okta group.
  3. Confirmed that groups created directly in ZIA do not appear as available options.

 

​


KeiK.29963 likes this.
  • Paul S. (Okta, Inc.)

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

     

    Based on your troubleshooting, your overall SAML and SCIM integration between Okta and Zscaler Internet Access (ZIA) is healthy, as standard provisioning and user sync are functioning correctly.

     

    The reason you are encountering the "No matches found" error during Group Linking is due to how Zscaler segregates directory sources and restricts SCIM API visibility.

     

    The Cause: Directory Segregation in Zscaler

    1. SCIM API Visibility Limits: When you attempt to link a group via Okta Push Groups, Okta sends an API query (GET /Groups) to ZIA's SCIM endpoint to search for the group name. However, Zscaler strictly isolates directory objects based on how they were originally provisioned (e.g., Local/Admin-managed vs. SCIM/IdP-managed).
    2. Local Groups are Hidden from SCIM: Because the existing okta-test2 group was created directly within the ZIA administration console, Zscaler flags its dictionary source as "Local" rather than "SCIM". For security and data integrity, Zscaler's SCIM API intentionally does not expose locally created groups to external SCIM clients. When Okta asks ZIA for a list of matching groups, ZIA returns an empty result.
    3. Missing SCIM Metadata: For Okta to link to a group, the target group must possess an externalId (the IdP SCIM Group ID) binding it to the SCIM directory context. Manually created groups in ZIA lack this metadata, and Zscaler does not allow a SCIM client to merge with or "take over" a local group to rewrite its identity source.

     

    The Resolution

    To successfully manage this group via Okta, you must allow Okta to act as the source of truth and create the group natively via the SCIM API. ZIA cannot retroactively link a local group to a SCIM group.

    Perform the following steps to resolve the issue:

    1. Remove the Local Group: Log into the ZIA administration console and delete the manually created okta-test2group.
    2. Note: Before deleting, check if this group is currently tied to any active ZIA policies (such as URL Filtering, SSL Inspection, or Cloud App Control). You will need to re-link these policies shortly.
    3. Push the Group from Okta: Navigate back to Okta > Applications > Zscaler Internet Access > Push Groups. Click the + Push Groups button and select Find groups by name. Search for okta-test2, ensure Push group memberships immediately is checked, and click Save.
    4. Verify the Sync: Okta will now automatically provision the group in ZIA. The push status in Okta should display as Active, and the group will appear in the ZIA Admin Console with its identity source correctly flagged as SCIM.
    5. Update ZIA Policies: Reattach the newly synchronized okta-test2 SCIM group to any necessary ZIA policies.

     

     

    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
    Selected as Best
  • Paul S. (Okta, Inc.)

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

     

    Based on your troubleshooting, your overall SAML and SCIM integration between Okta and Zscaler Internet Access (ZIA) is healthy, as standard provisioning and user sync are functioning correctly.

     

    The reason you are encountering the "No matches found" error during Group Linking is due to how Zscaler segregates directory sources and restricts SCIM API visibility.

     

    The Cause: Directory Segregation in Zscaler

    1. SCIM API Visibility Limits: When you attempt to link a group via Okta Push Groups, Okta sends an API query (GET /Groups) to ZIA's SCIM endpoint to search for the group name. However, Zscaler strictly isolates directory objects based on how they were originally provisioned (e.g., Local/Admin-managed vs. SCIM/IdP-managed).
    2. Local Groups are Hidden from SCIM: Because the existing okta-test2 group was created directly within the ZIA administration console, Zscaler flags its dictionary source as "Local" rather than "SCIM". For security and data integrity, Zscaler's SCIM API intentionally does not expose locally created groups to external SCIM clients. When Okta asks ZIA for a list of matching groups, ZIA returns an empty result.
    3. Missing SCIM Metadata: For Okta to link to a group, the target group must possess an externalId (the IdP SCIM Group ID) binding it to the SCIM directory context. Manually created groups in ZIA lack this metadata, and Zscaler does not allow a SCIM client to merge with or "take over" a local group to rewrite its identity source.

     

    The Resolution

    To successfully manage this group via Okta, you must allow Okta to act as the source of truth and create the group natively via the SCIM API. ZIA cannot retroactively link a local group to a SCIM group.

    Perform the following steps to resolve the issue:

    1. Remove the Local Group: Log into the ZIA administration console and delete the manually created okta-test2group.
    2. Note: Before deleting, check if this group is currently tied to any active ZIA policies (such as URL Filtering, SSL Inspection, or Cloud App Control). You will need to re-link these policies shortly.
    3. Push the Group from Okta: Navigate back to Okta > Applications > Zscaler Internet Access > Push Groups. Click the + Push Groups button and select Find groups by name. Search for okta-test2, ensure Push group memberships immediately is checked, and click Save.
    4. Verify the Sync: Okta will now automatically provision the group in ZIA. The push status in Okta should display as Active, and the group will appear in the ZIA Admin Console with its identity source correctly flagged as SCIM.
    5. Update ZIA Policies: Reattach the newly synchronized okta-test2 SCIM group to any necessary ZIA policies.

     

     

    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
    Selected as Best

Loading
Inquiry Regarding Group Linking for the “Zscaler Internet Access” Application Created from the OIN Catalog