Users should be persisted in separate context

[blcham]

Same way as it is done in fta-fmea tool.

A/C:

• Person is saved in separate context
• there is a migration script in migration directory to move Person entity from default context to the correct context (see example of such script here. I suggest to call it person-from-default-to-separate-context.ru.
• change configuration of keycloak to put users to the separate context

[blcham]

It would be easier to implement after #208

[palagdan]

@blcham,

It’s a bit confusing. I checked the implementation in FTA-FMEA and noticed that some users (test1 and test2) are in a separate context:
http://context-with-users

In the internal authorization, I created two users, and they are stored without a context:

I’m not sure which option I should implement in RM:

Create a new context for each user.
Use a common context, like http://context-with-users.

[blcham]

@palagdan All users should be in one context.

[blcham]

@palagdan I transfered this issue to record-manager-ui and updated A/C.

Please configure docker-compose.yml so that keycloak-graphdb-user-replicator puts users into separate context. It should be tested locally.

see https://github.com/kbss-cvut/keycloak-graphdb-user-replicator

and parameter NAMESPACE and DB_SERVER_CONTEXT

[blcham]

@palagdan I created PR for last point in A/C, please revise and make sure that you understand how it works.