Disconnected apps & connectors
Govern the apps with no API or connector.
learn more
Recommended reading
Closing the disconnected application gap.
See a Windows application and a terminal application brought under governance live, with no API and no code, then get a scoped plan to close the gap in your own…Extracting from a WebApp with no APIs.
Every application waiting in your onboarding queue is an application nobody governs. Without an API, each one becomes a custom connector project.Featured
Governance coverage that outlasts the IGA platform.
A regulated U.S. financial services company stopped a competing purchase after seeing READI live. It now onboards disconnected applications 10X faster, and that coverage will move with it to its…
All content
Connect Everything Identity with Connector Studio
I've been thinking a lot lately about connectors and how our core identity applications get the information they need. It seems like loading the data has always been a problem,…
Video
Bot Studio using REST
David Bullas shows you how to enable and execute bots using REST, making it simple to integrate with third-party applications and unlock the full potential of the READI platform. This…Your Identity Processes – Connect More!
According to some recent research by our friends at One Identity, only 8% of companies have fully automated provisioning processes and 70% rely upon manual operations for joiner / mover…
Blog
Random Acts of Identity Automation – Take the Quiz!
The problem IT shops are typically complex and managing an array of moving parts. Keeping identities provisioned, licensed and secure, involves endless touch points. There’s the basics of ensuring that…Governance coverage
Governing disconnected applications in your IGA.
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.
ten minutes, no sales call.