feat(iam-web): last-sync indicator for Directory Sync#5094
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Strix Security ReviewNo security issues found. Updated for Reviewed by Strix |
Contributor
QA ReportCommit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Last sync activity indicator to the Directory Sync surfaces — the SCIM card's Provisioning health panel and the setup wizard's verify panel.
Kortix is the SCIM server, so the honest signal we own is when the IdP last made an authenticated SCIM call — the backend already stamps
last_used_aton every validated request (including no-change reconciliation reads); this surfaces it, computed across active tokens only, polling live.Since the next sync time isn't knowable from the SP side, the indicator pairs the timestamp with each provider's real cadence (new
syncCadenceHintper SCIM guide): Entra's ~40-min scheduled cycle, event-driven pushes for Okta/OneLogin/JumpCloud, PingOne's full-then-incremental. This also replaces the wizard footer that hardcoded Entra copy for every provider. Freshness tint: green <5m / <1h, neutral when quiet (normal for event-driven IdPs), amber only when a token exists but the IdP has never connected.Also:
PUT /scim/v2/accounts/:accountId/Groups/:groupId— Okta pushes group renames as full-resource PUT; only PATCH existed, so those calls 404'd (the exact gap previously closed for Users PUT). Omitted fields are left alone; a presentmembersarray (even empty) is authoritative. Route manifest regenerated (+1 route), SCIM-3 flow covers PUT rename + unknown→404.Tests: pure helpers (
scim-sync.test.ts,parseGroupPut) + structural pins; web 79 pass, api 25 pass, coverage gate green, tsc/lint clean.