[Fiware-lab-help] FI-Lab Assistance

Álvaro Alonso aalonsog at dit.upm.es
Mon Apr 21 15:56:36 CEST 2014


Hi, 

as Javier says, I thought you are developing in FILAB (because this is the filab help list). 

Anyway, I've just updated also Testbed environment so you can test it. 

BR
-- 
Álvaro

El Apr 15, 2014, a las 2:38 PM, Dirk Krause escribió:

> ok - thanks!
> 
> Best,
>   Dirk
> From: javier cerviño [jcervino at dit.upm.es]
> Sent: Tuesday, April 15, 2014 1:12 PM
> To: Dirk Krause
> Cc: Álvaro Alonso; fiware-lab-help at lists.fi-ware.eu
> Subject: Re: [Fiware-lab-help] FI-Lab Assistance
> 
> Hi Dirk,
> 
> I guess Alvaro update the code in FI-LAB and not in Testbed, but we'll update also that environment next monday. Sorry for the inconvenience! 
> 
> Cheers,
> Javier.
> 
> 
> On 11 April 2014 15:57, Dirk Krause <dirk.krause at pixelpark.com> wrote:
> Unfortunately, it still doesn't work …?
> 
> XMLHttpRequest cannot load https://account.testbed.fi-ware.org/user?access_token=ekVCNQaPOBXss3lR_O3fObOePhgzoTF52JYqzcAsDD638b3g3U1gOxoTD6yxLz_zyAerqdb1Y3TFCLI-hBaPrQ. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8000' is therefore not allowed access.
> 
> From: Dirk Krause
> Sent: Thursday, April 10, 2014 3:32 PM
> To: Álvaro Alonso
> Cc: fiware-lab-help at lists.fi-ware.eu
> Subject: RE: [Fiware-lab-help] FI-Lab Assistance
> 
> Thanks!
> 
> We'll try this.
> 
> -- Dirk
> From: Álvaro Alonso [aalonsog at dit.upm.es]
> Sent: Thursday, April 10, 2014 3:11 PM
> To: Dirk Krause
> Cc: fiware-lab-help at lists.fi-ware.eu
> Subject: Re: [Fiware-lab-help] FI-Lab Assistance
> 
> Hi, 
> 
> I understand you refer to "Authorization" header. I've just updated CORS configuration whit that header. You can try it. 
> 
> BR
> -- 
> Álvaro
> 
> El Apr 8, 2014, a las 5:02 PM, Dirk Krause escribió:
> 
>> 
>> see below, please.
>> 
>> best, dirk
>> From: Tobias Rotter
>> Sent: Tuesday, April 08, 2014 4:59 PM
>> To: Dirk Krause
>> Subject: AW: [Fiware-lab-help] FI-Lab Assistance
>> 
>> Hey Dirk,
>>  
>> the problem seems to come with the AJAX-Request. If i try to open the URL manually it works great. But the AJAX-Request (same URL) in the application is canceled without any answer.
>>  
>> Maybe there is a Problem with the Request-Header?
>>  
>> Greetings,
>> Toby
>>  
>> --
>> Pixelpark AG, Geschäftsbereich Agentur, Tobias Rotter, Online Developer 
>> Cäcilienkloster 2, D-50676 Köln, Tel. +49.221.951515-227, Fax +49.221.951515-66
>>  
>> <image001.gif>
>> 
>> Web: http://www.pixelpark.com | Blog: http://www.wildpark.de/ | Twitter: http://www.pixelpark.com/twitter | Facebook: http://www.pixelpark.com/facebook
>> Firmensitz: Bergmannstraße 72, D-10961 Berlin, Vorstand: Horst Wagner (Vorsitzender), Dirk Kedrowitsch, Aufsichtsratsvorsitzender: Arthur Sadoun, Amtsgericht Charlottenburg: HRB 72163
>> This e-mail has been sent by Pixelpark AG, Germany. It is intended for the named recipient only. The information contained in this message and any attachments hereto are confidential and may be legally privileged. If you have received this e-mail in error or are not the intended recipient, please immediately notify the sender by return e-mail and delete this message and all attachments to it from your system without keeping a copy. Thank you for your cooperation.
>> <image002.jpg>Please consider your environmental responsibility. Do you really need to print this e-mail?
>>  
>> Von: Dirk Krause 
>> Gesendet: Dienstag, 8. April 2014 16:34
>> An: Álvaro Alonso; Tobias Rotter
>> Cc: fiware-lab-help at lists.fi-ware.eu
>> Betreff: RE: [Fiware-lab-help] FI-Lab Assistance
>>  
>> yes, we are still having problems.
>>  
>> We have Facebook and Github connect, both work fine. Trying the same code with fi-lab gives 403 errors.
>>  
>> @toby could you fill in some details?
>>  
>> best, dirk
>> From: Álvaro Alonso [aalonsog at dit.upm.es]
>> Sent: Tuesday, April 08, 2014 3:18 PM
>> To: Dirk Krause
>> Cc: fiware-lab-help at lists.fi-ware.eu
>> Subject: Re: [Fiware-lab-help] FI-Lab Assistance
>> 
>> Hi Dirk, 
>>  
>> yeah, it is enabled for Oauth2 paths. So it should work with your application. If you have any problem don't hesitate in ask again.
>>  
>> Best regards,
>> -- 
>> Álvaro
>>  
>> El Apr 7, 2014, a las 11:34 AM, Dirk Krause escribió:
>> 
>> 
>> Hi,
>>  
>>   did you enable CORS already?
>>  
>> Best,
>>   Dirk
>> From: Álvaro Alonso [aalonsog at dit.upm.es]
>> Sent: Friday, March 14, 2014 2:29 PM
>> To: Dirk Krause
>> Cc: fiware-lab-help at lists.fi-ware.eu
>> Subject: Re: [Fiware-lab-help] FI-Lab Assistance
>> 
>> Hi Dirk,
>>  
>> about the first question, we have not enabled CORS for OAuth requests.  Thanks for the notice. We are going to enable it in order to be compliant with all OAuth2 cases. However, you can use OAuth2 from your server side instead of from the client one. This way you will not have that problem.
>>  
>> About the second one, a colleague of mine will answer you shortly.
>>  
>> I hope this helps. Best regards
>> -- 
>> Álvaro
>>  
>> El Mar 13, 2014, a las 5:24 PM, Dirk Krause escribió:
>> 
>> 
>> Hi,
>>  
>> @OAuth
>>   we'd like to use the OAuth Authentification from an app and for that we need CORS enabled.
>> Is it possible to do that?
>>  
>> @chef
>>   is there an example Chef script we can use as a starting point for templates?
>> Best,
>>   Dirk
>> _______________________________________________
>> Fiware-lab-help mailing list
>> Fiware-lab-help at lists.fi-ware.eu
>> https://lists.fi-ware.eu/listinfo/fiware-lab-help
>>  
>> <403er-FILab2.png><403er-FILab.png>
> 
> 
> _______________________________________________
> Fiware-lab-help mailing list
> Fiware-lab-help at lists.fi-ware.org
> https://lists.fi-ware.org/listinfo/fiware-lab-help

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20140421/512dcf72/attachment.html>


More information about the Fiware-lab-help mailing list

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