Providers

The providers configuration controls which identity providers are enabled and how provider-specific behavior is applied. Use this file to enable providers, set priority and entrypoints, tune provider-specific session behavior, and apply capability-owned and feature-owned provider fields.

Capability-specific shared fields and provider-scoped capability overrides are documented under Capabilities. Conflict configuration for provider-owned conflicts is documented under Conflicts.

behavior

behavior contains shared runtime timings for all providers.

attemptTtl

• Takes: a positive duration
• Current default: "10m"
• Affects: how long provider-attempt markers stay in the replicated attempt store

Identica uses this when it marks that a provider attempt already happened for a provider, scope, username, and IP combination. Longer values make repeated attempts stay blocked longer. Shorter values let retries happen sooner.

behavior:
  attemptTtl: "10m"

{
  "behavior": {
    "attemptTtl": "10m"
  }
}

providers

• Takes: a list of provider entries
• Affects: provider enablement, ordering, entrypoint routing, provider-specific session behavior, capability and feature-owned provider overrides

Provider ids should match installed provider descriptors, such as premium or credential.

providers:
  - id: "premium"
    displayName: "PR"
    enabled: true
    priority: 100
    entrypoints:
      - "premium.example.com"
    session:
      concurrencyPolicy: "REJECT_NEW"

{
  "providers": [
    {
      "id": "premium",
      "displayName": "PR",
      "enabled": true,
      "priority": 100,
      "entrypoints": ["premium.example.com"],
      "session": {
        "concurrencyPolicy": "REJECT_NEW"
      }
    }
  ]
}

id

• Takes: a provider id string
• Affects: which installed provider descriptor this entry configures

This should match the provider's descriptor id exactly enough for case-insensitive lookup.

displayName

• Takes: a string
• Current default: ""
• Affects: the user-facing label used for this provider when one is needed

If this is blank, Identica falls back to the provider descriptor name and then the raw id.

enabled

• Takes: true or false
• Affects: whether the provider is available for resolution and flow building

priority

• Takes: an integer
• Affects: ordering when multiple providers are eligible

Higher values win before lower values.

entrypoints

• Takes: a list of hostnames, optionally with :port
• Affects: hostname-based provider selection before normal fallback ordering

Entries must use the format host or host:port. Leave the list empty if hostname-based provider selection is not part of your setup.

session

Use session when one provider should behave differently from the global live-session defaults.

session.concurrencyPolicy

• Takes: "ALLOW_MULTIPLE", "REPLACE_EXISTING", or "REJECT_NEW"
• Current default: absent
• Affects: how live-session replacement behaves for this specific provider

If this is absent, Identica uses settings.sessions.concurrencyPolicy.

capabilities

Use capabilities for provider-scoped fields owned by installed capabilities. Only providers that advertise a capability can use that capability's fields.

• Takes: an object keyed by capability id
• Current default: absent
• Affects: provider-scoped overrides contributed by capabilities

The shape inside capabilities is not global. Each installed capability defines its own nested fields.

Capability overrides are added manually inside a provider entry under capabilities.<capability-id>. Identica does not create these nested override blocks automatically just because a provider supports a capability.

If you want provider-specific behavior, add the capability block yourself. If you leave the block out, the capability continues to use its shared settings. If you add only some fields, only those fields are overridden and the rest continue using the shared capability configuration.

Basic shape:

providers:
  - id: "your-provider-id"
    capabilities:
      your_capability_id:
        someField: value

features

Use features for provider-scoped fields owned by installed features. Only installed features that extend provider configuration can use nested fields here.

• Takes: an object keyed by feature id
• Current default: absent
• Affects: provider-scoped overrides contributed by features

The shape inside features is not global. Each installed feature defines its own nested fields.

The official verification feature contributes verification here. See Verification settings.