Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Certificate Manager Web UI communicates with several components, for example, Protocol Gateway and Nexus Personal Desktop Client.

Overview

CM_WebUI_illustration-ppt.png

Detailed description of the communication flow

1

This section describes the green arrows in the illustration.

The user logs in to Certificate Manager Web UI via a URL in a web browser. When connecting, the web UI communicates with Protocol Gateway and activates the CM REST API.

  • Protocol Gateway communicates with Hermod. Hermod initiates the signing (sign-in process) and replies with a plug-out URL to Protocol Gateway.

  • Protocol Gateway sends the plug-out URL to Certificate Manager Web UI.


2

This section describes the orange arrows in the illustration.

Certificate Manager Web UI communicates with the middleware Nexus Personal Desktop Client (Classic).

  • Personal Desktop enables signing and authentication in web browsers without plugins, using the plugout technology, where Personal Desktop is triggered from the browser page.

  • Personal Desktop Client sends the login data to Hermod

  • Hermod sends a callback to Protocol Gateway

  • Protocol Gateway communicates with Certificate Factory (CF). This process verifies that the logged in user is an officer and if the user is an officer, the session is marked as authenticated and logged in.


3

This section describes the blue arrow in the illustration.

Certificate Manager Web UI verifies the sign in process, and if the process was successful, the web UI will start presenting data.

Additional information

  • No labels