Overview¶
Components of SEAL Operator/SEAL Print Client¶
SEAL Operator/SEAL Print Client includes the following components:
-
SEAL Operator
Main application as server for SEAL Print Client consisting of several microservices such as
seal-operator-server
,seal-operator-ui
orseal-operator-fileupload
-
SEAL Print Client
As Web user interface for creating output jobs, SEAL Print Client is provided as client for SEAL Operator.
-
Connector
A connector establishes the connection between the SEAL Operator server and the backend system.
-
OIDC Identity provider
The identity provider is a service connected with the OAuth 2.0/OpenID Connect (OIDC) protocol and is responsible for the user authentication and the mapping of rights and roles. A preconfigured Keycloak identity provider is provided by SEAL Systems for test purposes. In practice, another OIDC identity provider already installed at the customer's will be used for the user authentication and authorization. For more information about Keycloak and other OIDC identity provider used with SEAL Systems products, refer to the SEAL Interfaces for OIDC documentation.
-
Configuration service
The Consul configuration service provides the system configuration.
-
Credential store
The credential store administrates the user-specific credentials. In the standard installation, MongoDB is used as credential store.
-
Command line tool for administrators
With the command line tool, SEAL Operator CLI, the services of SEAL Operator can be managed and the configuration can be exported and imported.
-
Command line tool for users
With the command line tool, SEAL OP-CLI, the documents, tasks, panels and lists of SEAL Operator can be managed.