Thanks for the infos and points Ari & Philipp. I've followed the NGSI v2 discussions on their list and this seems like a good addition there. Lähetetty iPhonesta > Ari Okkonen ADT <ari.okkonen at adminotech.com> kirjoitti Jun 15, 2016 kello 9:40 AM: > > Hi Philipp, > > I made a ticket for CORS a long time ago: > https://jira.fiware.org/browse/HELP-6368 > > For the TCOR I now created the ticket > https://jira.fiware.org/browse/TCOR-253 > > Anyway, the final answer from Alvaro Alonso was: >> Hi Ari, >> yes, I know what CORS means. But as I said before, we have not it >> enabled in Horizon (Keyrock's front-end). I will include it as a feature >> to be explored in the future. We have to evaluate the impact it would >> have. >> Thanks for the suggestion. >> BR > > I guess the impact would be that the feature will be usable. > (If there were problems, Google and Facebook wouldn't have enabled > CORS, I think.) > > The reasons for the own authorization mechanism are: > 1. Easier to put to use in a non-FIWARE environment. Does not need > installing the FIWARE Security platform. > 2. Relatively easy to integrate other OAuth2 authentication services > (Twitter, Facebook, LinkedIn, X-Corporate-Internal, ...) as needed. > Google already integrated. > > BR > Ari > >> On 2016-06-15 06:57, < wrote: >> Hi Ari, >> Thanks for the update. >> That CORS thing is worth pushing for! Is there a ticket for this yet? >> Can you please create a ticket in the TCOR (technical coordination) >> section explaining in a bit mire detail what the issue is. I will then >> raise this in the Monday TSC call. >> It seems you to the Authentification via FIWARE but have you own >> Authorization mechanism. There is the option of doing this also via the >> GE for that. Have you looked into this? Is there a reason why you have >> gone for the current solution? >> Best, >> Philipp >>> Am 13.06.2016 um 13:33 schrieb Ari Okkonen ADT: >>> Hi Philipp, >>> Moreover, the problem with missing CORS support in KeyRock remains. E.g. >>> Google >>> and Facebook authentication servers support CORS, why does the KeyRock not? >>> This means that a client that got an authentication token from the >>> KeyRock server, >>> cannot ask who is hidden behind that token.So, the logged-in user is >>> shown as >>> "Keyrock User". >>> BR >>> Ari >>>> On 2016-06-13 12:03, Philipp Slusallek wrote: >>>> Hi, >>>> We just had the demo from the Security chapter. They seem to have a nice >>>> new feature to register "IoT sensors" under an account. Those sensors >>>> can actually be any app that can then use services on its own without >>>> using the personal account. This may be highly relevant for POI as well. >>>> See the first demo of today, right at the beginning of today's minutes >>>> (https://docs.google.com/document/d/1ilt-vkWAZZnOSG2vFk9tGYuQzP1sNr-Vf0GbBu6-3rk/edit#). >>>> BTW, what is the state of using FIWARE authentification with POI. I have >>>> not followed this in detail (sorry). >>>> Thanks, >>>> Philipp >> -- >> ------------------------------------------------------------------------- >> Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH >> Trippstadter Strasse 122, D-67663 Kaiserslautern >> Geschäftsführung: >> Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) >> Dr. Walter Olthoff >> Vorsitzender des Aufsichtsrats: >> Prof. Dr. h.c. Hans A. Aukes >> Sitz der Gesellschaft: Kaiserslautern (HRB 2313) >> VAT/USt-Id.Nr.: DE 148 646 973, Steuernummer: 19/673/0060/3 >> --------------------------------------------------------------------------- > > -- > Ari Okkonen > Adminotech > Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. > Please, send your messages using the new domain (Fiware-webui at lists.fiware.org) instead of the old one. > _______________________________________________ > Fiware-webui mailing list > Fiware-webui at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-webui
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy