[Fiware-security] URGENT Action points derived from architecture session on OAuth 2.0-based Access Control framework in FI-WARE

[Juanjo Hierro]

Hi all,

  This mail is a reminder of the several APs identified during our architect session on Monday 13th about the OAuth 2.0-based Access Control framework in FI-WARE.

  The first point had to do with making the GCP IdM GEi API documentation available to all partners.  You can now download the GCP IdM GEi API documentation from the following link at the FI-WARE project.   Note that access to this link is private, so you will have to login in your FusionForge account (and be registered as member of the FI-WARE project):

https://forge.fi-ware.eu/docman/view.php/7/2369/GCP+API+documentation_v0-2.pdf

  I have also attached to this email an updated version of the presentation that describes the architecture we are aiming to implement.

  As a follow-up of the technical session we had on Monday May 13th, I would like to remind the following action points:

  *   @UPM to carry out a revision of the RESTful API specification provided in the referred GCP documentation in order to determine if it  will allow them to finish developments under way regarding a FI-WARE OIL portal for management of user accounts and user attributes.   I remind to UPM that they should also rely on the available APIs from the Access Control GE to deal with definition of roles and access policies from the same portal.
  *   @UPM and @DT: UPM to provide detailed links to the places in the standard OAuth specs where they believe that the complete OAuth 2.0 RESTFul API to be supported by the IdM GE are specified.  DT to respond to UPM so that the whole issue about existence of a complete standard RESTful API is clarified.   Don't hesitate to carry out this discussion within the fiware-api-cross mailing list so that we can all follow-up the discussions
  *   @Thales to also carry out a revision of the GCP same documentation and design a proposal to present in our next follow-up confcall about how to manage updates of some attributes of users which may imply rejection of some request tokens (check last slide in the attached presentation)
  *   @UPM to confirm whether all the information is available for them to finalize development of the Proxy
  *   @NSN to confirm whether they plan to support a RESTful API in compliance with the GCP RESTful specification.   (note: NSN couldn't attend the confcall on May 13th but this issue was raised: there should be a single IdM GE RESTful API specification so either NSN is happy to implement the one provided by DT or both have to agree on one they will both support)

  You all are called to attend afternoon session during the next joint WPLs/WPAs follow-up confcall (14:30 to 16:00) on May 27th where we will have the opportunity to follow-up all the above APs (we will start the session addressing these points so that you don't need to stay the whole session if we finish earlier, but please book the whole slot in your agendas).

  Cheers,

-- Juanjo

-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Coordinator
and Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20130521/ac189b9e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FI-WARE Security 13-05-14.pptx
Type: application/vnd.openxmlformats-officedocument.presentationml.presentation
Size: 187888 bytes
Desc: not available
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20130521/ac189b9e/attachment.pptx>