Okta Identity Provider Group Assignment Options and Full Sync Behavior
Last Updated:
Overview
When administrators configure an external Identity Provider (IdP) for full group synchronization, Okta removes users from existing groups during the next sign-in because of group changes made in the external Identity Provider. Administrators can resolve unexpected group membership removals by reviewing the four available group assignment options and verifying configuration changes in the System Log.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Identity Provider (IdP)
- Group Assignment
- Just-In-Time (JIT) Provisioning
Cause
The issue originates in the external Identity Provider because administrators make group changes in the Identity Provider, not in Okta. When administrators set the group assignment configuration to full synchronization, Okta mirrors the group memberships provided in the SAML assertion during the next user sign-in. If administrators remove a group in the Identity Provider, the Identity Provider omits it from the assertion. This omission causes Okta to remove the user from the corresponding Okta group.
Solution
What are the available Identity Provider group assignment options?
Review the four available group assignment options and their expected behaviors to understand how Okta processes group memberships.
- None: Okta does not assign authenticated users to any groups. No other information is required.
- Assign to specific groups: Okta assigns users to specified groups. Enter the name of the group in the Specific Groups field, select the matching group, and repeat to add more groups.
- Add user to missing groups: Okta adds users to any groups in the Security Assertion Markup Language (SAML) assertion that they do not already belong to during Just-In-Time (JIT) provisioning. Okta does not remove users from existing groups. Enter the SAML attribute name representing group memberships in the SAML Attribute Name field. Okta compares the assertion values to the Group Filter field, which acts as a security allowlist. Enter the name of the group in the Group Filter field, select the matching group, and repeat to add more groups.
- Full sync of groups: Okta assigns users to the group represented by the attribute specified in the SAML Attribute Name field. Ensure that this group appears in the Group Filter field.
NOTE: If the user is a member of any group that does not match the values in the SAML attribute name field, Okta deletes the user from the group.
How do administrators verify Identity Provider configuration changes in the System Log?
Search the System Log for specific event types and review the target attributes to confirm group assignment configuration updates.
- Open the System Log.
- Enter
eventType eq "system.idp.lifecycle.update"in the search field. - Expand the event and review the Target section.
- Locate the Action attribute to identify the new configuration value along with the group details for group-specific configuration.
System Log Action Values for Group Assignment Options
Okta records specific action values in the System Log corresponding to each group assignment configuration option.
- None:
NONE - Assign to specific groups:
ASSIGN - Add user to missing groups:
APPEND - Full sync of groups:
SYNC
