--- title: "LDAP connector: setup and compatibility | Stacksync" description: "LDAP integration guide: plan Groups (groupOfNames / posixGroup), record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/ldap last_modified: 2026-09-15 --- Developer tools · Two-way sync platform # LDAP integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your LDAP workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Groups (groupOfNames / posixGroup). Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Entries** - **Person entries (inetOrgPerson / user)** - **Groups (groupOfNames / posixGroup)** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=ldap) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## LDAP records to discuss. These LDAP record examples help scope a technical review. They are not a list of verified Stacksync operations. Entries Identify this record type and the operation you need to review with Stacksync. Person entries (inetOrgPerson / user) Identify this record type and the operation you need to review with Stacksync. Groups (groupOfNames / posixGroup) Keep group IDs and membership relationships separately from group names. ### See 3 more record examples Organizational units (ou) Identify this record type and the operation you need to review with Stacksync. Attributes Identify this record type and the operation you need to review with Stacksync. Operational attributes Identify this record type and the operation you need to review with Stacksync. Connection setup ## LDAP connection requirements. Review LDAP access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the LDAP account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for LDAP, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your LDAP integration. Record the tenant, user identity, group membership, and approval authority for each lifecycle change. Reporting an account does not authorize provisioning, permission changes, or deactivation. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks LDAP **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Keep group IDs and membership relationships separately from group names. Load related records in the right order Resolve user and tenant identities before membership changes. ### Mapping checks by record type #### Groups (groupOfNames / posixGroup) Confirm object support with Stacksync Identity Keep group IDs and membership relationships separately from group names. Fields to consider Source group ID · Member references · Tenant reference · Group type Related records to resolve first Resolve user and tenant identities before membership changes. Test before going live Test removed membership, nested groups, and equal group names in different tenants. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the LDAP integration in four steps. A renamed login retains its identity, and access changes affect only the approved account and groups in the intended tenant. ### View the four setup tests and expected results 1. ### Verify LDAP connectivity and database privileges After confirming an implementation path, validate the selected access method from the integration network to the intended host, database, and schema. Have the administrator demonstrate the permissions required for both the first read and later change capture. **Expected result:** The approved role can access the selected data and capture later changes without depending on an administrator’s personal session. 2. ### Test record matching for Groups (groupOfNames / posixGroup) Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test removed membership, nested groups, and equal group names in different tenants. **Expected result:** A renamed login retains its identity, and access changes affect only the approved account and groups in the intended tenant. 3. ### Test the operation your workflow needs Review one LDAP record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your LDAP integration. ### Diagnose record matching, delayed changes, and rejected operations A LDAP record appears under the wrong destination record Keep group IDs and membership relationships separately from group names. Resolve user and tenant identities before membership changes. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected LDAP implementation’s change-detection method for Groups (groupOfNames / posixGroup). Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific LDAP object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your LDAP workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=ldap) ## LDAP integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## LDAP connector FAQ ### How should I plan an integration with LDAP? Record the tenant, user identity, group membership, and approval authority for each lifecycle change. Reporting an account does not authorize provisioning, permission changes, or deactivation. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the LDAP connector write changes back? Write-back support is not established for this connection. Review the LDAP records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for LDAP data? Keep group IDs and membership relationships separately from group names. ### Which related records should I load first for LDAP? Resolve user and tenant identities before membership changes. ### How do I validate LDAP changes after the initial load? Test removed membership, nested groups, and equal group names in different tenants. A renamed login retains its identity, and access changes affect only the approved account and groups in the intended tenant. ### What will we cover in a LDAP integration demo? Start with one workflow and a sample record from Groups (groupOfNames / posixGroup). We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up LDAP from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my LDAP and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use LDAP. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a LDAP record changes.” - “Create a Genie that answers questions about our LDAP data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore LDAP connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Active Directory and LDAP](https://www.stacksync.com/integrations/active-directory-and-ldap) - [GitHub and LDAP](https://www.stacksync.com/integrations/github-and-ldap) - [LDAP and Okta](https://www.stacksync.com/integrations/ldap-and-okta) - [LDAP and PostgreSQL](https://www.stacksync.com/integrations/ldap-and-postgresql) - [LDAP and Supabase](https://www.stacksync.com/integrations/ldap-and-supabase) - [LDAP and Slack](https://www.stacksync.com/integrations/ldap-and-slack) - [LDAP and Splunk](https://www.stacksync.com/integrations/ldap-and-splunk) - [LDAP and Rockset](https://www.stacksync.com/integrations/ldap-and-rockset) ### Database · 50 - [LDAP and Airtable](https://www.stacksync.com/integrations/airtable-and-ldap) - [LDAP and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-ldap) - [LDAP and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-ldap) - [LDAP and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-ldap) - [LDAP and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-ldap) - [LDAP and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-ldap) - [LDAP and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-ldap) - [LDAP and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-ldap) - [LDAP and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-ldap) - [LDAP and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-ldap) - [LDAP and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-ldap) - [LDAP and Citus](https://www.stacksync.com/integrations/citus-and-ldap) - [LDAP and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-ldap) - [LDAP and Couchbase](https://www.stacksync.com/integrations/couchbase-and-ldap) - [LDAP and DuckDB](https://www.stacksync.com/integrations/duckdb-and-ldap) - [LDAP and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-ldap) - [LDAP and Firebase](https://www.stacksync.com/integrations/firebase-and-ldap) - [LDAP and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-ldap) - [LDAP and Google Cloud Spanner](https://www.stacksync.com/integrations/google-cloud-spanner-and-ldap) - [LDAP and Google Cloud SQL](https://www.stacksync.com/integrations/google-cloud-sql-and-ldap) - [LDAP and IBM AS/400](https://www.stacksync.com/integrations/ibm-as400-and-ldap) - [LDAP and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-ldap) - [LDAP and IBM Informix](https://www.stacksync.com/integrations/ibm-informix-and-ldap) - [LDAP and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-ldap) - [LDAP and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-ldap) - [LDAP and JDBC](https://www.stacksync.com/integrations/jdbc-and-ldap) - [LDAP and MariaDB](https://www.stacksync.com/integrations/ldap-and-mariadb) - [LDAP and MarkLogic](https://www.stacksync.com/integrations/ldap-and-marklogic) - [LDAP and MongoDB](https://www.stacksync.com/integrations/ldap-and-mongodb) - [LDAP and MySQL](https://www.stacksync.com/integrations/ldap-and-mysql) - [LDAP and Neo4j](https://www.stacksync.com/integrations/ldap-and-neo4j) - [LDAP and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/ldap-and-oci-database) - [LDAP and OpenSearch](https://www.stacksync.com/integrations/ldap-and-opensearch) - [LDAP and Oracle DB](https://www.stacksync.com/integrations/ldap-and-oracle-db) - [LDAP and Postgres Heroku](https://www.stacksync.com/integrations/ldap-and-postgres-heroku) - [LDAP and PostgreSQL](https://www.stacksync.com/integrations/ldap-and-postgresql) - [LDAP and RavenDB](https://www.stacksync.com/integrations/ldap-and-ravendb) - [LDAP and Redis Enterprise](https://www.stacksync.com/integrations/ldap-and-redis-enterprise) - [LDAP and Reltio](https://www.stacksync.com/integrations/ldap-and-reltio) - [LDAP and Render Postgres](https://www.stacksync.com/integrations/ldap-and-render-postgres) - [LDAP and SAP ASE (Sybase)](https://www.stacksync.com/integrations/ldap-and-sap-ase-sybase) - [LDAP and SAP HANA](https://www.stacksync.com/integrations/ldap-and-sap-hana) - [LDAP and Scaleway Postgres](https://www.stacksync.com/integrations/ldap-and-scaleway-postgres) - [LDAP and SingleStore](https://www.stacksync.com/integrations/ldap-and-singlestore) - [LDAP and SQL Server](https://www.stacksync.com/integrations/ldap-and-sql-server) - [LDAP and Supabase](https://www.stacksync.com/integrations/ldap-and-supabase) - [LDAP and TiDB](https://www.stacksync.com/integrations/ldap-and-tidb) - [LDAP and TimescaleDB](https://www.stacksync.com/integrations/ldap-and-timescaledb) - [LDAP and VoltDB](https://www.stacksync.com/integrations/ldap-and-voltdb) - [LDAP and YugabyteDB](https://www.stacksync.com/integrations/ldap-and-yugabytedb) ### Data warehouse · 28 - [LDAP and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-ldap) - [LDAP and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-ldap) - [LDAP and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-ldap) - [LDAP and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-ldap) - [LDAP and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-ldap) - [LDAP and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-ldap) - [LDAP and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-ldap) - [LDAP and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-ldap) - [LDAP and BigQuery](https://www.stacksync.com/integrations/bigquery-and-ldap) - [LDAP and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-ldap) - [LDAP and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-ldap) - [LDAP and Databricks](https://www.stacksync.com/integrations/databricks-and-ldap) - [LDAP and Dremio](https://www.stacksync.com/integrations/dremio-and-ldap) - [LDAP and Exasol](https://www.stacksync.com/integrations/exasol-and-ldap) - [LDAP and Firebolt](https://www.stacksync.com/integrations/firebolt-and-ldap) - [LDAP and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-ldap) - [LDAP and Greenplum](https://www.stacksync.com/integrations/greenplum-and-ldap) - [LDAP and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-ldap) - [LDAP and Materialize](https://www.stacksync.com/integrations/ldap-and-materialize) - [LDAP and MotherDuck](https://www.stacksync.com/integrations/ldap-and-motherduck) - [LDAP and Rockset](https://www.stacksync.com/integrations/ldap-and-rockset) - [LDAP and Snowflake](https://www.stacksync.com/integrations/ldap-and-snowflake) - [LDAP and Starburst Enterprise](https://www.stacksync.com/integrations/ldap-and-starburst-enterprise) - [LDAP and StarRocks](https://www.stacksync.com/integrations/ldap-and-starrocks) - [LDAP and Teradata Vantage](https://www.stacksync.com/integrations/ldap-and-teradata-vantage) - [LDAP and Tinybird](https://www.stacksync.com/integrations/ldap-and-tinybird) - [LDAP and Vertica](https://www.stacksync.com/integrations/ldap-and-vertica) - [LDAP and Yellowbrick](https://www.stacksync.com/integrations/ldap-and-yellowbrick) ### Business productivity · 37 - [LDAP and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-ldap) - [LDAP and Agiloft](https://www.stacksync.com/integrations/agiloft-and-ldap) - [LDAP and Asana](https://www.stacksync.com/integrations/asana-and-ldap) - [LDAP and Atlassian](https://www.stacksync.com/integrations/atlassian-and-ldap) - [LDAP and Braze](https://www.stacksync.com/integrations/braze-and-ldap) - [LDAP and Campfire](https://www.stacksync.com/integrations/campfire-and-ldap) - [LDAP and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-ldap) - [LDAP and Customer.io](https://www.stacksync.com/integrations/customer-io-and-ldap) - [LDAP and Docusign](https://www.stacksync.com/integrations/docusign-and-ldap) - [LDAP and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-ldap) - [LDAP and Front](https://www.stacksync.com/integrations/front-and-ldap) - [LDAP and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-ldap) - [LDAP and Gainsight](https://www.stacksync.com/integrations/gainsight-and-ldap) - [LDAP and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-ldap) - [LDAP and GitHub](https://www.stacksync.com/integrations/github-and-ldap) - [LDAP and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-ldap) - [LDAP and Ironclad](https://www.stacksync.com/integrations/ironclad-and-ldap) - [LDAP and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-ldap) - [LDAP and Lemlist](https://www.stacksync.com/integrations/ldap-and-lemlist) - [LDAP and Microsoft 365](https://www.stacksync.com/integrations/ldap-and-microsoft-365) - [LDAP and Microsoft Dynamics 365](https://www.stacksync.com/integrations/ldap-and-microsoft-dynamics-365) - [LDAP and Microsoft Teams](https://www.stacksync.com/integrations/ldap-and-microsoft-teams) - [LDAP and Monday](https://www.stacksync.com/integrations/ldap-and-monday) - [LDAP and NextGen Healthcare](https://www.stacksync.com/integrations/ldap-and-nextgen-healthcare) - [LDAP and Notion](https://www.stacksync.com/integrations/ldap-and-notion) - [LDAP and Orderful](https://www.stacksync.com/integrations/ldap-and-orderful) - [LDAP and Quip](https://www.stacksync.com/integrations/ldap-and-quip) - [LDAP and Resend](https://www.stacksync.com/integrations/ldap-and-resend) - [LDAP and SendGrid](https://www.stacksync.com/integrations/ldap-and-sendgrid) - [LDAP and ServiceMax](https://www.stacksync.com/integrations/ldap-and-servicemax) - [LDAP and ServiceNow](https://www.stacksync.com/integrations/ldap-and-servicenow) - [LDAP and Slack](https://www.stacksync.com/integrations/ldap-and-slack) - [LDAP and Smartsheet](https://www.stacksync.com/integrations/ldap-and-smartsheet) - [LDAP and SysAid](https://www.stacksync.com/integrations/ldap-and-sysaid) - [LDAP and Twilio](https://www.stacksync.com/integrations/ldap-and-twilio) - [LDAP and Wrike](https://www.stacksync.com/integrations/ldap-and-wrike) - [LDAP and Zendesk](https://www.stacksync.com/integrations/ldap-and-zendesk) ### Analytics · 3 - [LDAP and Pendo](https://www.stacksync.com/integrations/ldap-and-pendo) - [LDAP and Splunk](https://www.stacksync.com/integrations/ldap-and-splunk) - [LDAP and Treasure Data](https://www.stacksync.com/integrations/ldap-and-treasuredata) ### Communications · 5 - [LDAP and Aircall](https://www.stacksync.com/integrations/aircall-and-ldap) - [LDAP and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-ldap) - [LDAP and Infobip](https://www.stacksync.com/integrations/infobip-and-ldap) - [LDAP and RingCentral](https://www.stacksync.com/integrations/ldap-and-ringcentral) - [LDAP and Zoom](https://www.stacksync.com/integrations/ldap-and-zoom) ### Security and identity · 6 - [LDAP and Active Directory](https://www.stacksync.com/integrations/active-directory-and-ldap) - [LDAP and Auth0](https://www.stacksync.com/integrations/auth0-and-ldap) - [LDAP and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-ldap) - [LDAP and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-ldap) - [LDAP and Okta](https://www.stacksync.com/integrations/ldap-and-okta) - [LDAP and OneLogin](https://www.stacksync.com/integrations/ldap-and-onelogin) ### Storage · 4 - [LDAP and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-ldap) - [LDAP and Box](https://www.stacksync.com/integrations/box-and-ldap) - [LDAP and Egnyte](https://www.stacksync.com/integrations/egnyte-and-ldap) - [LDAP and SharePoint](https://www.stacksync.com/integrations/ldap-and-sharepoint) SECURITY ## Security teams trust Stacksync As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | SOC 2 Type II | | | ISO 27001 | | | HIPAA BAA | | | GDPR | | | CCPA | | | DPF US-EU-UK-CH | → SECURITY WITH BENEFITS ### SSO & SCIM Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more. ### Alerts Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options. ### Secure connection options Securely connects to your systems with: [OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)