<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
BambooHR Imports Future Dated Values into Okta before Due Date
Lifecycle Management
Okta Integration Network
Okta Classic Engine
Okta Identity Engine
Overview

BambooHR incorrectly imports values with future dates into Okta user profiles, rather than current values.

Applies To
  • BambooHR
  • Profile Sourcing
Cause
Upon import, Okta does not differentiate between future dated values and current values as the Get API call for users contains the onlyCurrent=false header in order to bring over users who are in a pre-hire state.
Solution

The issue is mitigated by enabling the Timezone aware pre-hires feature from the BambooHR Okta integration > Provisioning > Integration page and clicking on the Save button.

Provisioning

Recommended content

Loading
BambooHR Imports Future Dated Values into Okta before Due Date