Introduction

​

1. Introduction to Lumos connectors

1. Describe: The connector tells Lumos what it supports (capabilities), how it authenticates, what types of resources and entitlements it manages, etc.
2. Configure: Lumos prompts the customer’s IT admin to provide credentials and any required settings for that specific app instance.
3. Use: Lumos calls the connector’s capabilities to read or update data (e.g., list accounts, create user accounts, assign entitlements, etc.).

​

2. Terminology overview

• Connector
  A connector is the code package that allows Lumos to communicate with a third-party app.
• Custom Connector
  A custom connector is typically built by a customer to manage an internal system or an app not publicly available.
• Capability
  A capability is a particular standardized action (or API) a connector can perform. Examples include listing user accounts, creating a user account, or assigning entitlements.
• On-premise Connectors
  When a connector is run on a customer’s own hardware/network, it is referred to as an on-premise (on-prem) connector.
• SDK
  The SDK is a Python library that provides tools and structures to simplify connector development.
• Account
  In Lumos, an account refers to a user or service account in the underlying app.
• Entitlement
  An entitlement is a form of access or permission within the underlying app—such as a role, group membership, or license assignment.
• Resource
  A resource is an object in the underlying app that can be assigned entitlements (e.g., a project, a team, or a repository). A global entitlement (like an app-wide admin role) has no specific resource context.

​

3. How connectors fit into the Lumos platform

1. Connector Discovery
   • Lumos can discover your connector by referencing its name or listing all connectors available on the local or on-prem environment.
   • The connector’s info capability describes its capabilities, how to authenticate, and what resource/entitlement types it can manage.
2. Customer Configuration
   • Using the schemas provided by the connector (for both auth and additional settings), Lumos renders a configuration form.
   • The customer IT admin fills in the required credentials (e.g., OAuth tokens, API keys, or Basic auth credentials) and chooses any optional settings.
3. Validation
   • Lumos calls the connector’s validate_credentials capability to ensure the provided credentials and configuration are valid.
4. Ongoing Operations
   • Whenever Lumos needs to list, read, create, or update resources/accounts/entitlements, it calls the appropriate connector capability.
   • For OAuth-based connectors, Lumos might also call capabilities to refresh tokens (refresh_access_token) or handle authorization flows.

​

Two ways to host connectors

1. Lumos-Hosted
   The connector code is loaded by Lumos directly as a Python module in a managed environment.
2. On-Premise (Customer-Hosted)
   The connector is packaged to run on a server within the customer’s network. Lumos interacts with it via CLI calls. Often used for apps behind firewalls or not accessible over the public internet.

​

4. Connector self-description (info capability)

• App Metadata
  A human-friendly name, logo URL, description, and a unique app ID.
• Authentication Schema
  A JSON schema describing how users can authenticate (Basic, Token, OAuth, etc.).
• Request Settings Schema
  A JSON schema for non-sensitive configuration fields (e.g., hostnames, toggles, or optional flags).
• Capabilities
  Which standardized actions (list, create, deactivate, etc.) the connector supports.
• Resource and Entitlement Types
  What resources and types of entitlements the connector can manage (e.g., “teams,” “groups,” “roles,” “licenses”).

{
  "response": {
    "user_friendly_name": "Pretend App",
    "description": "A pretend app for examples",
    "logo_url": "https://some-logo.com/pretend_app_logo.png",
    "app_id": "pretend_app",
    
    "authentication_schema": { ... },
    "request_settings_schema": { ... },
    
    "capabilities": [ ... ],
    "resource_types": [ ... ],
    "entitlement_types": [ ... ]
  }
}

 

​

5. Connector configuration: auth and settings

​

Auth

• Basic (username + password)
• Token (API key, bearer token, etc.)
• OAuth (access token, refresh token, client credentials, etc.)

​

Settings

• A custom domain or hostname to call the underlying app.
• A toggle for including certain data in responses.
• Default roles or groups to manage.

​

Validating credentials

​

6. Connector capabilities

• auth: Auth credentials.
• settings: Non-auth configuration data.
• request: Capability-specific parameters.
• response: The result data.
• page: A pagination token if you need to return more data in subsequent calls.

​

6.1 Metadata capabilities

• list_connector_app_ids
  Lists all connector app IDs available.
• info
  (Described above) Gives Lumos the connector’s metadata and capabilities.
• list_custom_attributes_schema
  Returns the schema for any custom attributes the connector supports.

​

6.2 OAuth capabilities

• get_authorization_url
  Returns the URL to initiate an OAuth flow.
• handle_authorization_callback
  Exchanges authorization codes for tokens.
• handle_client_credentials_request
  Handles the OAuth client_credentials (machine-to-machine) flow.
• refresh_access_token
  Refreshes an OAuth token using a refresh token.

​

6.3 Read capabilities

• list_accounts
  List user/service accounts in the app.
• list_entitlements
  List available entitlements (groups, roles, licenses, etc.).
• list_resources
  List resources (projects, teams, repositories, etc.).
• list_expenses
  Retrieve a list of reimbursements and/or card transactions
• find_entitlement_associations
  Show which entitlements go with which resources.
• get_last_activity
  Provide last activity data (e.g., last login) for specified accounts.
• validate_credentials
  Confirm credentials are valid, often used right after configuration.

​

Pagination

​

6.4 Write capabilities

• create_account
  Provision a new user in the underlying app.
• update_account
  Update an existing user account in the underlying app.
• activate_account
  Activate or reactivate a user account.
• deactivate_account
  Deactivate/suspend a user account.
• delete_account
  Permanently remove a user account.
• assign_entitlement
  Grant a user an entitlement.
• unassign_entitlement
  Revoke an entitlement from a user.

​

7. Deploying Lumos connectors

1. Lumos-Hosted
   • The connector is installed into a Python environment within Lumos.
   • Lumos imports and calls the connector’s functions directly in Python:
     from pretend_app import integration
     await integration.dispatch("list_accounts", '{"request": {}}')
     
2. On-Premise (Customer-Hosted)
   • The connector is packaged and installed on servers within the customer’s network.
   • Lumos interacts via CLI commands:
     pretend_app list_accounts --json '{"request": {}}'
     
   • Helpful when the underlying app is not accessible publicly or must remain on a private network.

​

How to run an on-prem agent locally

​

8. Building your own connector with the Lumos Python SDK

• Install the SDK
• Define Connector Info
  • Implement an info function (or use an SDK-provided structure) to specify the connector’s name, description, app ID, logo, capabilities, authentication, and settings schema.
• Implement Capabilities
  • For each capability (e.g., list_accounts, create_account), write the function that handles the request and returns a response in the standardized format.
  • If using OAuth, implement additional capabilities like get_authorization_url, handle_authorization_callback, etc.
• Test Locally
  • Test your connector by calling it locally, either via CLI or direct Python calls, to ensure it can connect to your app’s APIs and handle edge cases.
• Debugging
  • By default, the connector will log to a file in the directory {cwd}/logs with a default log level of ERROR in a file named {app_id}_{yyyy-MM-dd}.log
  • You can change the log level by setting the LUMOS_LOG_LEVEL environment variable with export LUMOS_LOG_LEVEL=DEBUG
    • Valid log levels are DEBUG, INFO, WARNING, ERROR, and CRITICAL.
  • You can also change the directory of the log file by setting the LUMOS_LOG_DIRECTORY environment variable with export LUMOS_LOG_DIRECTORY=./some_directory
    • When this is set, the connector will log to a file in the file {LUMOS_LOG_DIRECTORY}/{app_id}_{yyyy-MM-dd}.log
• Publish and Deploy
  • If Lumos hosts your connector, provide the code/package reference.
  • If you need on-prem, bundle the connector with the Lumos on-prem agent.

​

9. Putting it all together

1. Discovery
   • Lumos detects your connector and calls info.
2. Configuration
   • Lumos displays a form for an IT admin to enter auth credentials and settings, derived from your inforesponse.
3. Validation
   • validate_credentials confirms everything is correct.
4. Use Cases
   • list_accounts to view user accounts in the app.
   • create_account to provision a new user.
   • assign_entitlement to grant permissions or licenses.
   • get_last_activity for usage info.
5. Maintenance
   • Automatic OAuth token refresh via refresh_access_token.
   • Update connector settings or credentials as needed.

​

10. Next steps and references

• Lumos Connector Capabilities Detailed specs for each capability’s request/response fields.
• On-Premise Agent Instructions for installing and managing the on-prem agent on Windows or Linux.
• SDK on PyPI connector-py for the latest release and installation instructions.
• Custom Attributes If your app uses custom fields on accounts, see list_custom_attributes_schema.

​

Final thoughts

1. Describe (capabilities, authentication, schemas)
2. Configure (credentials, settings)
3. Use (read and write actions on users, entitlements, resources)