Groovy Script connector
To integrate with various applications and support Joiner, Mover, and Leaver processes, OpenIAM utilizes connectors. The role of connectors within the OpenIAM architecture is detailed in this document.
OpenIAM provides a variety of out-of-the-box connectors for commonly used on-premises and SaaS applications, such as Active Directory (AD), Entra ID, AWS, Google Workspace, SAP HANA, Oracle EBS, and more. These connectors enable seamless integration between OpenIAM and target applications by implementing an organization’s business requirements with minimal effort.
However, organizations often need to integrate OpenIAM with custom applications that lack a pre-built connector. These applications may have unique data structures, authentication mechanisms, or API endpoints, making standard connectors (e.g., SCIM or database connectors) insufficient. In such cases, organizations require a flexible integration approach that allows them to define their own logic while leveraging OpenIAM infrastructure.
To address these requirements, OpenIAM offers the following integration options.
- Groovy Script Connector. This is a connector framework based on Groovy, allowing implementers to focus on integration logic within Groovy scripts while OpenIAM handles the core connector functionality.
- PowerShell Script Connector being a connector framework based on .NET & PowerShell, enabling implementers to focus on integration logic in PowerShell scripts without needing to implement the core connector logic.
- Custom Java Connector is a fully custom connector developed in Java. This approach offers maximum flexibility but requires more development time compared to the scripted options above.
The documents in this section focus on the Groovy Script Connector, explaining its capabilities, structure, and implementation guidelines.