Architecture
Components
| Component | Role |
|---|---|
| Partner | The Partner's system |
| RMS API | API gateway that receives requests |
| Certificate Service | Provides certificate/credential information |
| Signing Service | Processes signing requests |
| INTRUSTCA | User confirmation channel for flows that require confirmation |
This diagram is a documentation model. Internal implementation details need to be cross-checked against the actual architecture before release.
The internal document "API Integration Installation Guide" describes a different model: the Partner self-hosts the "RMS API" cluster (Sign Server) on their own infrastructure, instead of calling the shared endpoint specified as the base URL in Environment. Both models may coexist (self-hosting for infrastructure control, or calling the shared endpoint directly) — see API Installation and confirm with the backend team which model applies before publishing officially.
Context: CTS Registration
Registering/issuing a CTS (digital certificate) for the end user is done through INTRUST's own portal (https://rmsportal.intrustdss.vn), which is outside the scope of the API described in this documentation. The Partner only needs to call the API after the CTS has been issued to the user. See details of the registration process, approval, and the overall integration diagram at CTS Registration & Issuance.
[TO CONFIRM] — the scope of Portal access (e.g., IP whitelisting, a dedicated admin account for the Partner) needs further confirmation with the INTRUST operations team.