Vendor registration
Each Local CMS needs a vendor registration at RI. The correct vendor must
be known and registered in RI for the clubs using the service. In order
to separate the SEMDA services, one vendor is
defined for each Local CMS. The corresponding vendor names using SEMDA
service are:
- SEMDA - CH&FL - Polaris
-
SEMDA - AT&BIH
- Polaris
-
SEMDA - BE&LUX
- Polaris
-
SEMDA - FR
- Polaris
-
SEMDA - SE
- Polaris
-
SEMDA - IS
- Polaris
- SEMDA - ES
- Polaris
-
SEMDA - DE - RoCas
-
SEMDA - DE - Aurora
-
SEMDA - NL
- SEMDA - FI
-
SEMDA - IT - 2032
-
SEMDA - IT - 2041/42
For new customers having a new Local CMS using SEMDA,
RCS will request RI to create a new vendor.
Authorization
The authorization to use the SEMDA systems is issued by the RCS. Respective product contract and SLA must be signed. RCS will then pass the required unique authentication key to the Local CMS. This key must be used for the connection to SEMDA and in all requests.
Authentication
Each request from Local CMS to SEMDA must contain a unique authentication key which identifies the Local CMS. This authentication key is created by the RCS and passed to the Local CMS after contract and SLA have been signed. Request without valid
authentication key are discarded.
Access and encryption
Access to SEMDA is possible only through https protocol.
All
data in transfer between Local CMS and SEMDA and between SEMDA and RI
is encrypted.
Data Security
SEMDA does not have persistent storage like a database. It uses a
reliable message broker (RabbitMQ) to temporarily store requests from
various Local CMS. The requests are managed in a queue, assigned to each
particular Local CMS. The request data is automatically destroyed when a
request has been processed. The reliability feature of RabbitMQ ensures
that the system survives a power failure or software crash without loss
of data.
The access to the request data is possible only through the
programmatic components of SEMDA. There is no GUI or tool to display the
request data available to the SEMDA customers.
SEMDA fulfills the highest security requirements because:
- No data is persistently stored in SEMDA
- No data is exposed to a user interface or an interactive tool.
- Data related to a particular Local CMS is separated and isolated from all other connected systems.
- The data exchanged between the particular Local CMS and RI is not passed to any other system.
