# OneLogin

Baton OneLogin Connector - Sync users, roles, and applications from OneLogin identity provider

## Prerequisites

- A Mesh administrator account with permission to manage connectors.
- `onelogin_client_id` — OneLogin API client ID (OAuth 2.0 client credentials)
- `subdomain` — OneLogin subdomain (for example yourcompany for yourcompany.onelogin.com)
- `privileges_enabled` (optional) — When true, syncs OneLogin privileges in addition to roles
- Credentials for authentication: onelogin_client_secret (stored write-only).

## Authentication

**Method:** Bearer token

Mesh authenticates with a token (personal access token, API token, or bot token).

| Field | Required | Secret | Description |
| --- | --- | --- | --- |
| `onelogin_client_secret` | Yes | Yes (write-only) | OneLogin API client secret (stored as secret) |

## Capabilities

<CapabilityMatrix
  capabilities={[
    { name: "Identity & entitlement sync", supported: true },
    { name: "Writeback / remediation", supported: false, notes: "Read-only" },
  ]}
/>

## Data model

_This information is not yet available from the connector schema._

## Setup

1. Gather the required value: `onelogin_client_id`.
2. Gather the required value: `subdomain`.
3. Gather the required value: `privileges_enabled`.
4. Create the required credentials in the source system: onelogin_client_secret.
5. In Admin → Connectors, add the connector and enter its configuration.
6. Save and run an initial collection.

## Troubleshooting

_This information is not yet available from the connector schema._