[Fiware-testbed] threat for the adoption of the fi-ware testbed!

Sandfuchs, Thorsten thorsten.sandfuchs at sap.com
Mon Oct 8 08:41:20 CEST 2012


Hi Stefano,
Is there a support from RED.es or the Testbed for issuing the needed ssl-certificates for port 443?

I think if we go for SSL we shouldn't go for self-signed certificates as this would be the next complaint we might get.

The problem is: certificates aren't for free.

The first option would be to have a trusted CA sign the CAs (which comes at a cost).

The second option might be that we issue certificates with an own CA and a given user would have to adopt "only" the FI-WARE CA once, and then would have access to the SSL-enabled Testbed. But this would impose additional knowledge and work on the user and on our side.

In both cases we should have a clear statement for our stakeholders on what to do.

What do you or the others think?

Best regards,
                                                                /Thorsten

From: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] On Behalf Of stefano de panfilis
Sent: Montag, 8. Oktober 2012 03:21
To: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Cc: fiware-testbed at lists.fi-ware.eu
Subject: [Fiware-testbed] threat for the adoption of the fi-ware testbed!

dear all,

as you know the uc projects are studying the work we are doing and in many cases, after an initial draft evaluation, really interested in adopting in their prototypes our generic enablers.

here it comes a barrier at which we did not put initially too much attention: it this the port on which the ges communicate.
in several case the port is not the standad one i.e. by default, a corporate internet proxy will normally allow the standard HTTP/HTTPS ports - 80 and 443.

this fact, although cannot be seen as a wrong or incomplete installation per se, basically prevents sevareal uc to effectively use and integrate the generic enablers they are interested in.
since the succes of fi-ware is fully based on the adoption of our technologies (please ref. to the last review report), the above circumstance making extremely difficult the validation by the uc projects, basically poses fi-ware on the wrong side of success as the uc projects will issue the concern the testbed is not usable ...!!!

to this extent i kindly ask you:
1. to change the communication port to be a standard port;
2. to complete this change by wednesday e.o.b this week (i.e. 10 october);
3. consequently to update the catalogue.

this way on thursday the tesbed team can validate the changes and than i can communicate we have fixed this, i.e. to put the uc projects back in front of their responsibility.

thank you in advance for your prompt collaboration on the matter.
please notify henar, miguel and me when done.

ciao,
stefano




--
Stefano De Panfilis
Chief Innovation Officer
Engineering Ingegneria Informatica S.p.A.
via Riccardo Morandi 32
00148 Roma
Italy

tel (direct): +39-068307-4295
tel (secr.): +39-068307-4513
fax: +39-068307-4200
cell: +39-335-7542-567
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-testbed/attachments/20121008/d7829ba9/attachment.html>


More information about the Old-Fiware-testbed mailing list

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