[Fiware-lab-recovery-tf] question from arian

Federico Michele Facca federico.facca at create-net.org
Wed May 20 16:18:59 CEST 2015


hi stefano,

i think the issue is related to the missing support of implicit
authentication from new idm. as for the infographic, they could solve by
using a user account for now and the basic authentication.

federico

On Wed, May 20, 2015 at 4:13 PM, stefano de panfilis <
stefano.depanfilis at eng.it> wrote:

> dear federico,
>
> many thanks, we second federico position and, in case, happy to understand
> all the implications.
>
> please note that from yesterday i received a complain from fi-c2 platform
> providers that while their platform, deployed in the lannion node was very
> well working before the deployment of the new idm, since then is not
> working any longer.
>
> they properly issued a ticket in jira, but things apparently are stacked.
> somehow i'm suprised about having this kind of results which i think
> should be addressed with high priority as our users should be considered
> all as customers, in particular when they are good and positive with
> respect to fiware.
>
> can alvaro/federico/fernando have a look on this? or telling me anything
> so i can make aware peter on the evolution of the situation?
>
> i cannot attend our daily meeting today. apologises.
>
> thank you in advance.
>
> ciao,
> stefano
>
> 2015-05-20 15:36 GMT+02:00 Federico Michele Facca <
> federico.facca at create-net.org>:
>
>> dear juanjo,
>> my 2 cents on arian's question:
>>
>> The problem mentioned by arian is not solved, since idm/keystone is a
>> single central service not high available in multiple locations beyond
>> spain (such as the portal) - which does not reflect openstack usual
>> architecture deployment for multi-region openstack. The default
>> architecture for multi region keystone could not be applied since it
>> requires to host user data outside spain.
>>
>> CREATE-NET proposed a solution (which was having a single keystone per
>> node) using delegation to authenticate users using oauth2 from the "main"
>> keystone, the advantages of such solution would have been:
>>    a - nodes don't fail when central keystone is not available.
>>    b - nodes can support both local users and FIWARE Lab users making
>> "entering in the game" for without funding much cheaper
>>
>> the solution would require anyhow:
>>    - requires some changes in portal
>>    - requires some changes in blueprint engine
>>
>> thus basically - eventhough developed and partially tested - it was not
>> moved ahead.
>>
>> alternative solutions may be based on saml, but i have the feeling this
>> will get more complex for the portal and blueprints.
>>
>> best,
>> federico
>>
>>
>> --
>> --
>> Future Internet is closer than you think!
>> http://www.fiware.org
>>
>> Official Mirantis partner for OpenStack Training
>> https://www.create-net.org/community/openstack-training
>>
>> --
>> Dr. Federico M. Facca
>>
>> CREATE-NET
>> Via alla Cascata 56/D
>> 38123 Povo Trento (Italy)
>>
>> P  +39 0461 312471
>> M +39 334 6049758
>> E  federico.facca at create-net.org
>> T @chicco785
>> W  www.create-net.org
>>
>> _______________________________________________
>> Fiware-lab-recovery-tf mailing list
>> Fiware-lab-recovery-tf at lists.fiware.org
>> https://lists.fiware.org/listinfo/fiware-lab-recovery-tf
>>
>>
>
>
> --
> Stefano De Panfilis
> Chief Innovation Officer
> Engineering Ingegneria Informatica S.p.A.
> via Riccardo Morandi 32
> 00148 Roma
> Italy
>
> tel (direct): +39-06-8759-4253
> tel (secr.): +39-068307-4513
> fax: +39-068307-4200
> cell: +39-335-7542-567
> skype: depa01
> twitter: @depa01
>
>


-- 
--
Future Internet is closer than you think!
http://www.fiware.org

Official Mirantis partner for OpenStack Training
https://www.create-net.org/community/openstack-training

-- 
Dr. Federico M. Facca

CREATE-NET
Via alla Cascata 56/D
38123 Povo Trento (Italy)

P  +39 0461 312471
M +39 334 6049758
E  federico.facca at create-net.org
T @chicco785
W  www.create-net.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-recovery-tf/attachments/20150520/a0e9fcfd/attachment.html>


More information about the Fiware-lab-recovery-tf mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy