Knowhow build up about the use of keycloak in marketplace

[akrguda]

As a developer I want to get the knowhow about how to use keycloak and its possibiltiy for using it in marketplace so that I can use it for database solution questions / security and so on.

DoR

• [ ] We got a story about the possibility using keycloak elements. In this case it is Ticket https://github.com/AkrosAG/Akros-Marketplace/issues/182

---

Acceptance Criteria

• [ ] AC1: The knowhow about using parts of keycloak is build up and documented
• [ ] AC2: The knowhow about where our keycloak server runs (inhouse / internet and country and company) is up to date.
• [ ] AC3: For the ticket 182 we know wheter it is worth to use components from keycloak instead of our table advertiser or not
• [ ] AC4: In case of using keycloak elements instead of table we know which table we will drop and how to use keycloak instead
• [ ] AC5: In case of using keycloak elements we have a new ticket that specifiy each step to get keycloak in use in marketplace

---

DoD

• [ ] We got the knowhow about using keycloak
• [ ] Because of the huge possibility of keycloak the analysed parts are documented
• [ ] The decision is done about we will use keycloak for fulfill ticket 182 or we handle it as it is designed today.
• [ ] We got an estimation about how many days it takes to change the current databasemodel with the keycloak solution
• [ ] When we use keycloak we got a new ticket in which every step to change the use of database and so on is documented

[Filipe-Inacio]

After what I learned about keycloak it does not make sense to connect our db with this from keycloak because it is a system that works perfectly how it is.

For the marketplace that means know that we have 2 possibility how resolve the ticket #182

1. Save userId on the topic At the moment we are saving on the topic an userId that comes from keycloak. With that we can show our adds and everything. That would also be a little bit the easier way

2. After register save the created user from Keycloak in our advertiser table As soon as we have registered the user in keycloak, we would need to store it also in our table. So that would mean we save the information twice and for making one register we would need 2 requests