Topic starter
25/08/2026 9:13 am
TL;DR: Connector upkeep is a lasting identity burden, with Opnova saying changes in applications, schemas, and authentication rules keep integrations from staying finished. Identity governance needs lifecycle ownership and sustained coverage tracking, or stale sync can quietly separate policy from actual access state.
Editorial analysis by NHI Mgmt Group, based on content published by Opnova: “The Connector Treadmill: Why Integration Never Ends”.
Key questions
Q: Why do identity governance programmes spiral into long, expensive projects?
A: They spiral when manual discovery, schema mapping, review handling, and connector maintenance are treated as normal work rather than implementation debt.
Q: What are the signs that connector-based governance is failing?
A: Look for connectors that still report healthy while entitlements stop syncing, audits uncover stale access data, or the team spends most of its time rebuilding existing integrations instead of onboarding new ones.
Q: How should IAM teams handle applications that never stay stable enough for a fixed connector?
A: Treat those applications as lifecycle-managed integration problems, not one-off projects.
Practitioner guidance
- Budget for connector maintenance as a recurring control cost Separate initial build effort from year-on-year connector upkeep, testing, and rework.
- Classify silent sync failure as control drift Monitor for connectors that report healthy while entitlements, approvals, or identity attributes stop updating correctly.
- Prioritise applications with the highest maintenance load Rank integrations by rebuild frequency, change rate, and audit impact so the team focuses on the connectors consuming the most time and risk first.
Bottom line: Identity integration is not a one-time implementation task, because every connector becomes an ongoing maintenance obligation as applications and access models change.
Glossary terms: Connector lifecycle, Silent sync failure, Intent-driven automation, Governance Coverage Drift
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
25/08/2026 9:14 am
Connector lifecycle debt is the real identity integration problem: the hidden cost is not initial build effort but the continuous labour needed to keep integrations aligned with changing applications. That maintenance debt accumulates across each custom connector, turning IGA from a project into an operating model. Practitioners should judge integration programmes by lifecycle cost, not go-live success.
A few things that frame the scale:
- Nearly 60% of IT leaders cite restrictive cost and complexity as a weakness of legacy identity governance, according to the 2025 State of Identity Governance Report.
A question worth separating out:
Q: Should organisations replace brittle connectors with intent-driven automation?
A: Only where the maintenance burden of the connector is clearly greater than the governance value it delivers. Intent-driven automation can reduce fragility for changing applications, but it still needs evidence, approval gates where required, and continuous testing against the real estate.
👉 Read our full editorial: The connector treadmill exposes the real cost of identity integration