JDBC Connector
The JDBC Connector enables Strivacity to synchronize identities from relational databases using JDBC. It runs as part of the Directory Connector and communicates with Strivacity while maintaining connectivity to your database.
Unlike the LDAP Connector, the JDBC Connector retrieves identity data by executing SQL queries configured in an inbound connection. The connector periodically retrieves its configuration from Strivacity, executes the configured queries against the target database, and reports synchronization status and statistics.
Before you begin
Before configuring the JDBC Connector, ensure that:
- An identity store has been created in Strivacity.
- You have the identity store's Client ID and Client secret.
- The Directory Connector is installed and running.
- You have a JDBC driver for your database.
Configure the connector
Configure the Directory Connector to operate in JDBC mode and connect to your Strivacity tenant.
Configure connector authentication
The connector authenticates to Strivacity using the Identity Store credentials.
- In the Admin Console, navigate to Identities and Identity stores.
- Select an identity store.
- Under the Configuration tab, navigate to Directory Connector settings.
- Copy the Client ID.
- Copy the Client secret.
- Configure these values in the connector.
Configure the operation mode
Configure the connector to operate in JDBC mode.
datastoreType: jdbc_aggregation| Setting | Description |
|---|---|
datastoreType | Specifies the connector operating mode. Set this value to jdbc_aggregation to enable JDBC synchronization. |
Configure scheduling
The connector periodically retrieves configuration updates from Strivacity and sends heartbeat information.
connector:
inboundJdbc:
scheduling:
heartbeatInitialDelay: 5s
heartbeatInterval: 30s| Setting | Description |
|---|---|
heartbeatInitialDelay | Time to wait after the connector starts before retrieving configuration from Strivacity and sending the first heartbeat. |
heartbeatInterval | Frequency at which the connector checks for new configuration and sends heartbeat information. |
Configure retry behavior
Configure how the connector retries failed requests after receiving an HTTP 4xx response from Strivacity.
connector:
inboundJdbc:
failureAttemptCycleCount4xx: 3failureAttemptCycleCount4xx | Specifies how many synchronization cycles the connector retries an unchanged request after receiving a 4xx response from the cloud. |
Configure Redis
Configure the Redis settings used by the connector.
spring:
data:
redis:{redis_configuration}For information about Redis configuration, see the Spring Data Redis documentation.
Install JDBC drivers
The connector requires a JDBC driver for each database that it connects to.
- Obtain the required JDBC drivers for your database connections.
- Mount the directory containing the JDBC drivers to the connector Docker container under the
/workspace/BOOT-INF/lib/path. - During startup, the connector loads the available JDBC drivers from the mounted directory.
Multiple JDBC drivers can be installed simultaneously.
Configure an inbound connection
After the connector has been configured, create an inbound connection in Strivacity.
The inbound connection defines:
- the JDBC connection URL
- authentication credentials
- synchronization schedule
- SQL queries
- identity correlation
- attribute mappings
- synchronization behavior
For detailed instructions, see Inbound connection.
Verifying the connection
After configuring the connector and the inbound connection:
- Start the connector.
- Verify that the connector successfully authenticates with Strivacity.
- Verify that the inbound connection configuration is retrieved.
- Run an initial synchronization using a small data set.
- Confirm that identities are imported successfully.
Updated about 6 hours ago

