[Fiware-lab-recovery-tf] [Idm / Keystone] Unable to retrieve the Tenant information

[Álvaro Alonso]

Hi Stefano, 

I found the JIRA ticket and I’ve just answer him. 

BR
-- 
Álvaro

> El 21 May 2015, a las 09:08, Álvaro Alonso <aalonsog at dit.upm.es> escribió:
> 
> Hi Stefano, 
> 
> could you send the JIRA ticket? If you don’t have it, I will answer him directly via email.
> 
> BR
> -- 
> Álvaro
> 
>> El 20 May 2015, a las 16:33, stefano de panfilis <stefano.depanfilis at eng.it <mailto:stefano.depanfilis at eng.it>> escribió:
>> 
>> dear alvaro and federico,
>> 
>> here is the email from pieter i was mentioning few minutes ago in another email thread.
>> i think at least an answer like "we are taking care of your issue" should be sent and even having sent earlier.
>> 
>> indeed the new idm, without prior notice, put in truble one of our good users.
>> i think some support should also be given to them if the solutions should be only found at client side which, however, apparantly is not the case.
>> 
>> i suggest alfonso to create a specific item in our action plan as idm is a key element for fiware lab proper functioning and we have to keep maximum control over its evolution.
>> 
>> thank you all for your help on the matter.
>> 
>> ciao,
>> stefano
>> 
>> ---------- Forwarded message ----------
>> From: Van Der Linden Pieter <Pieter.VanDerLinden at technicolor.com <mailto:Pieter.VanDerLinden at technicolor.com>>
>> Date: 2015-05-20 14:25 GMT+02:00
>> Subject: FW: [Idm / Keystone] Unable to retrieve the Tenant information
>> To: stefano de panfilis <stefano.depanfilis at eng.it <mailto:stefano.depanfilis at eng.it>>
>> Cc: Travert Serge <serge.travert at technicolor.com <mailto:serge.travert at technicolor.com>>
>> 
>> 
>>  
>> 
>>  
>> 
>> Dear Stefano,
>> 
>>  
>> 
>> Further to our discussion at the sustainability workshop yesterday, I hereby transmit you the ticket posted by Geoffroy Chollon from Thales.
>> 
>> Geoffroy is the main engineer in charge of the “Runner” module of FIC2Lab. This module allows customers to instantiate a media&content enabler on FIWARE lab just by clicking on a button.
>> 
>> Geoffroy has found workaround to a number of bugs but he now is stuck because of the below reported problem. Due to this problem launch of FIC2Lab has already been delayed by 2 weeks now.
>> 
>>  
>> 
>> The below ticket has been posted yesterday, after other tickets posted by Mario Lopez-Ramos last week. For the moment we have had no response.
>> 
>> Would you please be so kind to address this question with the colleagues from FIWARE Lab and possible raise the priority of this ticket in their list.
>> 
>> FI-Content2 has a review next week focusing mainly on FIC2Lab. It would be pity to have to say we tried hard but it does work.
>> 
>>  
>> 
>> Many thanks,
>> 
>>  
>> 
>>                                                                 Pieter
>> 
>>  
>> 
>> P.S.: We are really looking forward to discuss future sustainability projects, however we believe that the first step is to make sure there is indeed something to be sustained.
>> 
>>  
>> 
>>  
>> 
>> From: CHOLLON Geoffroy [mailto:geoffroy.chollon at thalesgroup.com <mailto:geoffroy.chollon at thalesgroup.com>] 
>> Sent: mercredi 20 mai 2015 10:37
>> To: Van Der Linden Pieter
>> Subject: FW: [Idm / Keystone] Unable to retrieve the Tenant information
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> [@@ THALES GROUP INTERNAL @@]
>> 
>>  
>> 
>> From: CHOLLON Geoffroy 
>> Sent: mardi 19 mai 2015 18:03
>> To: 'fiware-lab-help at lists.fi-ware.org <mailto:fiware-lab-help at lists.fi-ware.org>'
>> Subject: [Idm / Keystone] Unable to retrieve the Tenant information
>> 
>>  
>> 
>> Hello
>> 
>>  
>> 
>> I am trying to convert an Idm token to a Keystone token. To do so I need the OpenStack tenant Id.
>> 
>>  
>> 
>> Due to the upgrade my previous api call (GET on https://cloud.lab.fiware.org/keystone/v2.0/tenants <https://cloud.lab.fiware.org/keystone/v2.0/tenants> with the Idm token) seems obsolete.
>> 
>> So I tried use the call described in the KeyRock documentation: https://account.lab.fiware.org/user?access_token=xxxxxxxxxx <https://account.lab.fiware.org/user?access_token=xxxxxxxxxx> .
>> 
>>  
>> 
>> But my problem is that my request does return a partial result:
>> 
>>  
>> 
>> >    curl -k -X GET https://account.lab.fiware.org/user?access_token=CtoNc8gdMmeWsrPAE6bYy4NfYbPBOj <https://account.lab.fiware.org/user?access_token=CtoNc8gdMmeWsrPAE6bYy4NfYbPBOj>
>> >    {"organizations": [], "displayName": "Mario L____-____s", "roles": [{"name": "provider", "id": "106"}], "app_id": "1d75df2ec0c1478db98a3c8db3169d63", "email":
>> 
>> >    "mario.l________s at t_________p.com <mailto:mario.l________s at t_________p.com>", "id": "mario-l____-____s"}
>> 
>>  
>> 
>> The ‘organizations’ field is empty when I use this call with a token bound to my Idm application. (As a side not, if I “steal” and use the idm token of the cloud portal I obtain with this call a populated list with the data I require .)
>> 
>>  
>> 
>> So is there an another way to retrieve an user tenant id by using the Idm token ?. Or should I somehow change my application in the Idm ?.
>> 
>>  
>> 
>>  
>> 
>> Thanks
>> 
>> Geoffroy
>> 
>>  
>> 
>> [@@ THALES GROUP INTERNAL @@]
>> 
>>  
>> 
>> 
>> 
>> 
>> -- 
>> 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
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-recovery-tf/attachments/20150521/344d9dd4/attachment.html>