Thales connector
Configure the Thales connector to provision users to the Thales (SafeNet Trusted Access) platform over its REST API.
The Thales connector (thales-connector-rabbitmq) provisions users to the Thales SafeNet Trusted Access identity and authentication platform over its REST API, using the endpoint and credentials from the managed-system configuration.
Create / update user (Save)
✅
Delete user
✅
Suspend / resume user
✅
Reset password
✅
Search users
✅
Login
✅
Search groups
✅
Test connection
✅
Group create/delete
❌ Not implemented in the current connector
Use cases
Full user-lifecycle provisioning to Thales SafeNet Trusted Access — create, update, suspend/resume, password reset, removal.
Importing Thales users and groups into OpenIAM via synchronization.
If you must create or delete Thales groups from OpenIAM, use the Thales WSDL connector instead.
Versions and compatibility
The end application is Thales SafeNet Trusted Access, reached over its REST API. Every endpoint is scoped to a tenant, so the tenant identifier is part of the path rather than a header.
Platform
Thales SafeNet Trusted Access
Interface
REST API v1, over HTTPS
Host
The managed system's URL
Path shape
/api/v1/tenants/{tenant}/... — users, groups and applications
Test connection
/api/v1/tenants/{tenant}/authorized
Prerequisites
A Thales service account with API credentials for your tenant.
Network access from the connector host to the Thales API base URL (HTTPS).
Installing the connector
Kubernetes
In Kubernetes deployments, the connector is deployed as part of OpenIAM — enable it in your deployment configuration; no separate installation is required.
RPM
Run the connector JAR directly:
Or, when managed by systemd, use the connector service unit (openiam-connector@thales-connector-rabbitmq). To deploy on a separate host, see Connectors via RPM.
Starting, stopping, and restarting
RPM (systemd)
systemctl start|stop|restart openiam-connector@thales-connector-rabbitmq
RPM (manual)
Start with the java -jar command above; stop by killing the process.
Kubernetes
kubectl rollout restart the connector deployment.
Command-line parameters and properties
The connector is a Spring Boot application. Its defaults ship inside the jar, and you override them in either of two places:
An external property file, read at
${confpath}/conf/properties/thales-connector-rabbitmq.properties. The file is optional, andconfpathis itself a system property, set with-Dconfpath=/data/openiam/.Directly on the command line, as
-Darguments, which win over the file.
org.openiam.connector.queue
THALES_Connector_1_Request
Must match the connector record exactly.
org.openiam.connector.queueResponseName
THALES_Connector_1_Response
org.openiam.connector.name / .type
THALES / THALES Connector
org.openiam.update.site.role
false
Controls whether the user's site role is updated during provisioning.
The connection details themselves are not set here — they are managed system parameters, covered under Configuring the managed system.
Verifying the connector is running
In the Webconsole, open the managed system — the Running connector status indicator must be green.
Click Test Connection — it must return success.
In the RabbitMQ management console, confirm the THALES_Connector_1_Request queue exists and has a consumer.
Check the connector log for startup errors.
Troubleshooting
Connector never receives messages
Queue-name mismatch
The connector record's queue must equal THALES_Connector_1_Request exactly.
API calls rejected by Thales
Wrong URL or service-account credentials
Verify the managed system's URL/Login/Password.
Site role not updating on provisioned users
org.openiam.update.site.role is false (default)
Set the property to true and restart the connector.
Group create/delete does nothing
Group-object operations are not implemented in the REST connector
Use the Thales WSDL connector for group provisioning.
See also: general connector troubleshooting and the connector error-code reference.
Registering the connector in OpenIAM
Register the connector under Provisioning → Connectors and attach it to the managed system — see Registering the connector.
Configuring the managed system
URL
The Thales API base URL for your tenant.
Login / Password
The API credentials for the Thales service account.
Attribute mapping and policy map
Map OpenIAM user attributes to the Thales user fields in the managed system's policy map.
Reconciliation and synchronization
The user and group searches supply Thales records as source data. Configure a sync against the managed system as described in Configuring synchronization.
Last updated
Was this helpful?