[Fiware-technical-committee] Current authentication model in the IoT stack and implications/relations with the evolution of IDM.

[Federico Michele Facca]

Dear All,
Looking at the code of the IoT Stack, it looks like the “domain” and “project” concepts of Keystone is used as way to
support multi-tenant management in different services (i.e. what is usually referred to as  service and service path).

http://fiware-iot-stack.readthedocs.io/en/latest/authentication_api/index.html

In my understanding, while FIWARE IDM was build on top of Keystone to OAuth2 in the cloud part, this never meant
that the Keystone APIs were to go to be official APIs for authentication. But I may be wrong…

If I am correct, then, while I understand the importance of supporting multi-tenancy, I wonder if this is the correct way in the context of FIWARE IDM APIs.

Also I wonder what’s going to happen to the services using this approach once we proceed with the evolution of the split
between the Cloud domain and the Lab domain. Is there going to be any impact?

Best,
Federico


Dr. Federico Michele Facca
Head of Martel Lab

Martel Innovate
Dorfstrasse 73 - 3073 Gümligen (Switzerland)
0041 78 807 58 38
0041 31 994 25 25
martel-innovate.com <http://martel-innovate.com/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-technical-committee/attachments/20170428/5673c719/attachment.html>