RHDS (Reusable HR Data Service)
AlertEnterprise·AE_HSc_RHDS_RestConnectorGuide
Overview
The RHDS connector integrates AlertEnterprise Guardian with RHDS (Reusable HR Data Service) — another AlertEnterprise-developed HR normalization layer, distinct from hrds-rest in that RHDS uses GraphQL rather than OData. The same naming-vs-protocol mismatch as ssg-entre-rest applies: "Rest" in the package name; GraphQL queries on the wire.
Both authentication paths are supported: OAuth 2.0 client credentials and Basic auth — the deployment chooses which based on customer policy.
For deployments standardized on OData / multiple-API-families, prefer hrds-rest. RHDS is the GraphQL-based alternative.
Architecture
Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.
Authentication
2 methods supported
OAuth 2.0 client credentials grant — typical preferred auth.
Basic auth supported as an alternative when the deployment can't accommodate OAuth.
Prerequisites
Everything that must be in place for this connector to work, with the owner who's responsible.
RHDS 8.4+ deployment with API access
customerAn operational RHDS deployment exposing GraphQL APIs.
Known limitations
Documented constraints to set customer expectations before deployment.
"Rest" in the name; GraphQL on the wire
informationalSame naming quirk as ssg-entre-rest. Operators expecting REST endpoints should expect GraphQL queries/mutations instead. AE's REST connector framework hosts the connector; the wire protocol downstream is GraphQL.
HR specifics
- Sync modes
- full-load · delta
- Direction
- inbound
- Contingent worker support
- Yes
- src/connectors/rhds-rest/source.pdf — Full connector guide — 56 pages, updated 2025-11-04
- src/connectors/rhds-rest/source.pdf — p5 — Supported Version