Limosaidentity
← All integrations

Standards & custom · CONNECTOR GUIDE

SCIM 2.0
Connected to governance.

Manage accounts and groups through a SCIM v2 endpoint.

SCIM 2.0Configurable operations

HOW IT FITS TOGETHER

Connect inventory.
Follow changes through.

Import observed accounts and access, then use configured policies and approved requests to drive supported changes.

SCIM 2.0 integration architecture
01 / SOURCE SYSTEM

SCIM 2.0

Accounts and groups

SCIM 2.0
Read inventory
02 / CONNECTION

Limosa connector

Authenticate · read · normalize

Import &
correlate
03 / GOVERNANCE

Identity & access

Inventory · policy · review evidence

← Supported changes return through the connector

Configured target operations execute after the relevant policy and approval steps. Subsequent reads provide observations of the result.

Conceptual architecture, not a product screenshot. Approval, execution and observed access remain distinct.

SUPPORTED FEATURES

What you can do.

These operations are configurable. Enable only the operations supported by your target and validate their mappings.

  • Import inventory

    Read the connector’s supported records into Limosa.

  • Create accounts

    Create accounts using required target attributes and mappings.

  • Update accounts

    Update the account attributes supported by this connector.

  • Enable accounts

    Apply the provider-specific enable or reactivation operation.

  • Disable accounts

    Apply the provider-specific disable, suspension or unlicensing operation.

  • Remove accounts

    Apply the provider-specific removal or deprovisioning operation.

  • Assign access

    Add a supported direct entitlement membership.

  • Remove access

    Remove a supported direct entitlement membership.

PREPARE YOUR CONNECTION

Start with the right scope
and credentials.

Configure the SCIM base URL, authentication, resource mappings and supported operations for your target.

Credential type

Application credential

Provider documentation ↗ (opens in a new tab)

Connection settings

Configure the application connection, credentials, account schema and operation mappings in the application editor.

Store credentials through the application’s credential controls or an approved external secret reference. Confirm roster visibility and review import policy before the first full import.

FROM CONNECTION TO GOVERNANCE

Map & correlate

Choose stable identifiers, map source attributes and link accounts to the right governed identities.

Review the inventory

Check imported records and memberships. Resolve unexpected gaps before relying on the connection for governance.

Enable changes deliberately

Configure supported writes, test the target behavior and follow provisioning history separately from approval decisions.

FULL AI SUPPORT

Your workflow.
Your AI assistant.

Operate and configure Limosa through an MCP-compatible AI assistant. The full management interface is available to AI, with the same permissions, validation and audit trail as the web workspace.

Start with https://identity.limosa.io/mcp. No existing Limosa account needed: sign in and create your workspace when prompted.

Connect your assistant ↗

YOUR NEXT STEP

See governance in practice.

Explore the public demo or bring your applications and governance questions to a guided conversation.