Duplicated Okta user in Hexnode (can’t delete)……Solved

Participant
Discussion
4 months ago Jan 08, 2026

Hey everyone, running into a weird directory glitch and hoping someone here has seen this before. 

I’ve got a user who is showing up twice in our Hexnode portal with two different hexnode IDs (433 and 423). I checked Okta, and there is definitely only one active account for this person on that end. 

I tried to just delete the duplicate record directly in Hexnode, but it blocks the deletion, saying it can’t be removed because the origin is synced from okta. I initiated a manual Okta sync from the hexnode side hoping it would reconcile and merge the records, but the ghost duplicate is still hanging around. Thankfully, it’s just this one user affected. 

The only clue I have: this specific user had a weird Apple DEP enrollment certificate issue a while back, which I suspect might be the root cause of the split record. Unfortunately, I can’t access the user portals directly right now to investigate the backend mapping. 

Any ideas on a quick workaround to get this device enrolled today? And does anyone know how to clear out that ghost record for good? 

Replies (1)

Marked SolutionPending Review
Participant
4 months ago Jan 09, 2026
Marked SolutionPending Review

Hey @annemie,

I’ve run into this before. It usually happens if a device enrollment and an Okta sync happen at the exact same time and confuse the system. Hexnode creates a temporary user record for the new device but then fails to combine it with the real account when Okta syncs over. Because Hexnode sees both of those records as “managed by Okta,” it locks you out of deleting them manually to protect the sync.

To get the device deployed today, just enroll it without authentication. Once the device shows up in your console, just select it, go to Actions > Change Owner, and assign it to the correct Okta user.

To actually clean up the ghost record:

  1. Remove the user from the Hexnode sync group over in Okta.
  2. Force a sync in Hexnode (this should wipe out both records).
  3. Add the user back to the Okta group and sync again to pull a clean, single ID.

Hope this helps!

Save