<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
0D54z00009n959wCAAOkta Classic EngineIntegrationsAnswered2023-11-07T23:55:09.000Z2023-11-02T15:30:21.000Z2023-11-07T23:55:09.000Z

UKG-Okta OOTB integration fails to recognize termination

Hello,

 

I am working on setting up UKG as a profile master through Okta OOTB integration. While user creation and update functioning as expected, the user record when terminated in UKG never gets deactivated in Okta. We believed this could be because of Active Directory being set as another profile source, the deactivation event switches the profile source from UKG to AD.

 

However, our test account was never provisioned in AD and the profile says, 'profile sourced from UKG'. Also disabled "Profile & Lifecycle Sourcing" in AD integration but no luck.

 

Additional information is, alongside the termination, UKG sets up termination date and reason. While these changes comes through as update to the profile, the deactivation is ignored.

 

I have a backup solution through Okta workflows to manage the deactivation but looking to have this in the OOTB integration so we will have one less thing to manage.

 

Please advise if anyone has a fix/workaround for this issue.

 

Thanks,

Sasi

 

(email redacted by Moderator)


This question is closed.
Loading
UKG-Okta OOTB integration fails to recognize termination