CTS Registration & Authentication
RMS supports Subscribers registering for/being issued a CTS (digital certificate) and confirming signatures via 2 methods:
- Native Device Authentication — register/issue a CTS and confirm signing directly on the INTRUSTCA MOBILE APP (eKYC in the app, signing confirmation, with the option to keep a session via biometric authentication).
- PIN Code Authentication — register/issue a CTS via the Portal (web), confirm signing by entering a PIN code along with the signing request.
Terminology
| Term | Meaning |
|---|---|
| CTS | Digital Certificate |
| CKS | Digital Signature |
| RMS (Remote Signing) | Remote Signing |
| Subscriber | The end-user using/subscribing to the provider's service |
| eKYC | Identifying the Subscriber via electronic means |
| PORTAL | The information channel supporting Subscribers in submitting CTS issuance applications and managing their CTS (https://rmsportal.intrustdss.vn) — used in the PIN Code Authentication method |
| MOBILE APP (INTRUSTCA) | The mobile app of the public CKS service provider, supporting eKYC for CTS issuance and signing confirmation — used in the Native Device Authentication method |
| DSS-MDS | The CTS management application of the DSS provider |
| CoreCA | The core system that processes eKYC, OTP, and CTS issuance |
| Partner's internal application (ERP/CRM/HIS, etc.) | The internal management application of the connecting organization (Partner) |
| SDK (Software Development Kit) | A library that supports the integration |
| API (Application Programming Interface) | A standard communication protocol for connecting applications |
Comparing the 2 methods
| Criteria | Native Device Authentication | PIN Code Authentication |
|---|---|---|
| CTS registration/issuance | Directly on the INTRUSTCA MOBILE APP (eKYC in the app) | Via the Portal (web), application reviewed by email |
| Confirmation when signing | Confirm on the INTRUSTCA MOBILE APP, with the option to keep a session (biometric authentication) | Enter a PIN code along with the sign request |
| Related APIs | login, sign (without pinCode) | login, sign (is_use_pin_code + pinCode) |
| API Reference | API Reference — Native Device | API Reference — PIN Code |
| CTS registration/issuance details | See details → | See details → |
Once the CTS has been issued (via either of the 2 methods above), the Partner calls the RMS API to perform the signing operation via the common flow — see Integration Flow.
API/SDK Integration Resources
The Partner can choose to integrate via API or SDK, applicable to both authentication methods above:
- API integration: see Quick Start and API Reference. If you need to self-host the API on your own infrastructure, see API Installation. Sample project (Example Demo): Download.
- SDK integration: see Integration Methods: API & SDK. Sample project (Example Demo): Download.