Mobile-ID · Digital Trust
ISO/IEC 27001 · FIDO2 · OpenID — View scope
Mobile-ID Sign · INTEGRATION & PRACTICE

RS-HUB and RSS documentation

Connect the Agent VNeID journey with Remote Signing Service documentation, keeping data sharing, signing-provider and source-system roles distinct.

Understand roles in the RAR/RS-HUB route

Roles and scope
ComponentResponsibility
User/VNeIDConfirms actions or information sharing under the applicable journey.
RAR/RS-HUBThe centralized signing-gateway scope is described in the public source; connectivity lists must be dated.
Signing providerCertificates and signature creation under the configured service.
Integrating applicationRetains documents, correlation, outcomes and validation under deployment boundaries.
Compare CAs and publication dates

RSS is the name in the supplied specification. Its deployment-specific relationship with RS-HUB must be confirmed; the two scopes are not merged into a new API.

Data sharing differs from signature generation

VNeID data-sharing consent → sharing outcome → signing request processing → signature data → final document and validation. The Viewer diagram does not clarify VNeID assembling; confirm it before describing a complete flow.

Sources and boundaries

Source scope
ComponentSourceRole and limit
RSS Specification1.11.260911Remote Signing Service; the document title alone does not confirm the full RS-HUB scope.
Agent recordingVNeID / WordObserved actions; not evidence that every provider is active in production.
Source applicationRecord and versionPrepare content, persist references, reconcile and validate results.

Kafka in the Specification describes internal service flows. Do not expose it as a browser integration or turn internal topics into customer webhooks.

Read RSS operations and confirmation items

From VNeID to the signing outcome

  1. Prepare the request

    Choose an eligible credential/provider and retain document version and RP reference.

  2. Await VNeID action

    The user reviews and consents to sharing scope. Sharing success is not signing completion.

  3. Track signing outcome

    Persist service x-billcode-id; receive callbacks or reconcile status before recreating a request.

  4. Assemble and validate

    Bind signatures to the prepared content and validate in the applicable trust context.

Watch registration and Word signing

RSS provider identifiers

Catalog from §1.3 — PDF page 6
IdentifierEvidence scope
HUD-CA2Listed in Specification 1.11.260911; current deployment connectivity requires separate confirmation.
HUD-VNPT-SMARTCAListed in Specification 1.11.260911; current deployment connectivity requires separate confirmation.
HUD-MISAListed in Specification 1.11.260911; current deployment connectivity requires separate confirmation.
HUD-SDSListed in Specification 1.11.260911; current deployment connectivity requires separate confirmation.
HUD-VT-CAListed in Specification 1.11.260911; current deployment connectivity requires separate confirmation.
HUD-FPT-CAListed in Specification 1.11.260911; current deployment connectivity requires separate confirmation.
HUD-BKAV-CAListed in Specification 1.11.260911; current deployment connectivity requires separate confirmation.
HUD-CMC-CAListed in Specification 1.11.260911; current deployment connectivity requires separate confirmation.
REFERENCE

Exception lane and recovery responsibility

If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.

Exception lane and recovery responsibility
OutcomeApplication / operator action
Cancel or denyReturn the user outcome; do not initiate signing.
Timeout or expired challengeReconcile first; create a new request only with renewed user confirmation.
Callback state mismatchReject and investigate correlation, session and redirect binding.
Attribute unavailable or deniedApply business policy; never substitute inferred identity data.
Signing provider unavailablePreserve the uncertain state; reconcile or escalate without silently switching routes.
REFERENCE

Responsibility boundaries and evidence

If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.

Responsibility boundaries and evidence
ComponentResponsibilityEvidence to review
EnterpriseBusiness record, representative authority and acceptanceRecord reference, version and approval
Mobile-IDContract-scoped orchestration, correlation and handoffRequest, callback, state and audit
RAR/C06 / VNeIDApplicable identity / attribute serviceAuthentication result and consent scope
CA / RSSPSigning credential and signature creationCertificate, signed output and verification

Compare with Viewer actions

Watch the appropriate route, read outcomes and omissions, then consult the operation. Videos do not replace contracts or validation reports.

Watch seven Viewer/VNeID recordings

Search Mobile-ID Sign

Local search inside the offline package.