Disconnected apps & connectors

Govern the apps with no API or connector.

A disconnected application is an application that an IGA platform cannot reach through a native connector, an API, or a standard protocol such as SCIM. Legacy line-of-business systems, homegrown tools, Win32 desktop software, mainframe and terminal environments, and niche SaaS products often fall into this group. Disconnected applications are where identity governance coverage ends.

Why disconnected applications create risk.

When an application sits outside your IGA, accounts in it are created and removed by hand. Access reviews skip it or rely on spreadsheet exports. Offboarding depends on someone remembering to log in and disable the account. These systems often hold sensitive data, so the gaps they leave tend to surface during audits as orphaned accounts and excess privileges.

How teams bring them under governance.

No single method fits every application. Applications with APIs can use an API connector. Those that export files or expose a database can use file-based or ODBC connectors. Applications without APIs, exports, or database access need a different approach.

READI’s Smart Connector uses AI and computer vision to navigate an application’s interface from plain-English instructions and turns that into a governed script. Connector Studio covers the rest with low-code connectors built on PowerShell that your own team can build and own. In both cases, identity data is cleansed and normalized before it reaches your IGA, so access reviews start from accurate information.

What you will find on this page.

This page collects demos, articles, and a webinar on closing the application coverage gap. Watch data extracted from a web application with no API, see a user deprovisioned in a terminal application, and read why the connector gap persists across IGA vendors.

Govern Every Application

ten minutes, no sales call.

You've seen the average.
Get your own number.