๐Ÿ”Œ Connector SDK

Extensible development framework for building tailored integrations with custom apps/systems while maintaining enterprise governance standards.

Overview

For truly unique or proprietary systems without standards-based integration methods, Lumos offers a Connector SDK. This toolkit allows developers to create bespoke connectors that fit your organizationโ€™s specialized workflows and data models. By extending the Lumos platformโ€™s core capabilities, you can ensure no system is left behind in your identity governance strategy.

Key Features

  • End-to-End Connector Lifecycle: Create, test, deploy, and maintain custom connectors within a unified framework.
  • Event-Driven Flows: Invoke custom logic at specific points in the provisioning lifecycle, such as before user creation or after an update.
  • Comprehensive Documentation: Lumos provides detailed guides, sample code, and best practices for building robust, secure connectors.

Real-World Example

  • Scenario: A services firm has a 20-year-old mainframe-based risk management tool that is critical for compliance. By writing a custom connector, the firm integrates it with Lumos to automate user onboarding, role assignment, and periodic access reviews.
  • Outcome: The once siloed mainframe system now participates in the companyโ€™s identity governance program, significantly reducing the manual effort of provisioning and auditing high-risk access.
  • Implementation: Used the Connector SDK to create a connector implementing system-specific protocols, with full support for provisioning, deprovisioning, and access reconciliation.

Benefits

  • Complete Framework: Comprehensive development tools and utilities.
  • Flexible Architecture: Support for various protocols and data formats
  • Enterprise Readiness:Built-in support for caching, logging, and monitoring

Considerations

  • Requires installing and configuring the Lumos Agent on-premise, which may involve firewall rules and server provisioning
  • Must maintain development expertise for custom connectors
  • Need to implement proper testing and validation procedures
  • Should document connector implementation and maintenance procedures

Whatโ€™s Next