User data

User data request

There is the legal requirement that on a user’s request it must be provided all stored data and information related to the user.

Following primary assets pa contain user-related data:

PA-Dashboard configuration accessed and stored via supporting asset SA-Web Portal core service
PA-User settings accessed and stored via SA-Web Portal core service

Required information^[1]:

User Id
Tenant Id
Valid user token from (any) user

Requesting user profile from portal/coreservice

Endpoint: \http://<core-container-domain>/api/v1/<tenant-id>/user-profile
Description: Returns the stored user profile of a user
Authentication: Authorization: bearer <token>
HTTP-Method: GET
<core-container-domain>: The internal cluster address of the core service container
<tenant-id>: The MACMA tenant id of the user
<token>: Any valid user token from the same tenant which is used in the request

Requesting dashboards from portal/coreservice

With the first endpoint only the header data of the user’s dashboard is returned, after getting all dashboard headers you need to request the full dashboard data using the dashboard ids from the headers endpoint response.

Endpoint: \http://<core-container-domain>/api/v1/<tenant-id>/dashboardHeaders/<user-id>
Description: Returns the headers of all stored user dashboards
Authentication: Authorization: bearer <token>
HTTP-Method: GET
<core-container-domain>: The internal cluster address of the container
<tenant-id>: The MACMA tenant id of the user
<user-id>: The MACMA id of the user
<token>: Any valid user token from the same tenant which is used in the request
Endpoint: \http://<core-container-domain>/api/v1/<tenant-id>/dashboards/<user-id>/<dashboard-id>
Description: Returns the stored dashboard with dashboard id <dashboard-id>
Authentication: Authorization: bearer <token>
HTTP-Method: GET
<core-container-domain>: The internal cluster address of the container
<tenant-id>: The MACMA tenant id of the user
<user-id>: The MACMA id of the user
<dashboard-id>: A dashboard id from the previous headers request
<token>: Any valid user token from the same tenant which is used in the request

User data deletion

There is a legal requirement that on user deletion all user related data must be removed.

Following primary assets contain user-related data:

PA-Dashboard configuration accessed and stored via SA-Web Portal core service
PA-User profiles accessed and stored via SA-Web Portal core service

Owner of tenants and users is MACMA, when a tenant or user is removed, MACMA sends a RabbitMQ message to the system exchange.

Web Portal listens to these messages and automatically removes the user and tenant related data.

1. See MACMA documentation