Fiware tenant integration

what: For the city of Tampere we need tighter integration with Keyrock IDM. If you have some data to push in to the system, that needs permissions. At the moment all that data needs to be entered in Keyrock IDM / Umbrella.

why: Jumping back and forth between different domains and logins is disrupting the Ux and not in a good way. Users need to do their stuff in single place, which is APInf platform.

how: Expose a few fields in UI and POST that to IDM / umbrella

assumptions:

Keyrock (IDM) is in play
Business ecosystem (BE) is in play

TODO:

create a settings.json where IsFiwareIDMCOnfigNeeded = true / false - create separate task [ ]
create a settings UI where Admin can configure IDM URL etc. Shown if settings.json has IsFiwareIDMCOnfigNeeded = true - create separate task [ ]
create a tenant UI. That data is then POSTed / GET to IDM API / umbrella - create separate task [ ]
work out the underlying business logic for the task above - create a separate task [ ]
outline how this works when BE monetization is integrated - create a separate task [ ]

NOT TODO:

save any duplicate data to local DB if it can be avoided. Query status from IDM / umbrella.
do any choices that prevent further Business API ecosystem integration or make it harder

questions:

what APIs does the business ecosystem have?

reference: https://business-api-ecosystem.readthedocs.io/en/latest/index.html https://fiware-idm.readthedocs.io/en/latest/

After this: This is the seller part. After this the user / API(data) owner can go to BE and list the product(API/data) for sale. need to neatly integrate that too.

apinf / platform

Fiware tenant integration #3657