[Fiware-idm-ge] Input needed on supported protocols

[Antonio Tapiador del Dujo]

El 25/09/13 15:52, DANGERVILLE Cyril escribió:
>
> Hello,
>
> Sorry I was not at the conf call, but I just have 3 comments from the 
> point of view of the Access Control GE integration:
>
> 1)It would help to have SCIM features marked "OPTIONAL" as specific 
> rows in the SCIM REST API table, the same way you did for "Bulk":
>
> *3.2.2.2* 
> <http://tools.ietf.org/html/draft-ietf-scim-api-02#section-3.2.2.2>*.  
> Filtering*
>
>
>           3.2.2.3
>           <http://tools.ietf.org/html/draft-ietf-scim-api-02#section-3.2.2.3>. 
>           Sorting
>
>
>         (and also 3.3.2
>         <http://tools.ietf.org/html/draft-ietf-scim-api-02#section-3.3.2>. 
>         Modifying with PATCH, but less important to the AC GE)
>
>
>     4 <http://tools.ietf.org/html/draft-ietf-scim-api-02#section-4>. 
>     Multi-Tenancy
>
> 2)For multi-tenancy in NSN, it is said:
>
> "Tenant ID may be specified in HTTP header according to 4.1.3."
>
> Is it not possible to use 4.1.1 URL prefix as well, like for the oauth 
> Token Info request ? (See DigitalSelf-AC_GE.doc that Gabor sent me).
>
> 3)I am missing a feature like  "OAuth Token Info/Validation API" (the 
> equivalent of the Token Info mentioned in the previous point). This is 
> quite important to the Access Control GE to be able to validate/get 
> info about an OAuth access token, as you know. The issue is that it is 
> not part of the standards as far as I know (?), so I let you decide 
> where it would fit.
>
>

I don't know the Token Info request described in DigitalSelf-AC_GE.doc, 
but I would say at UPM we are using the /user call described before as a 
way to validate the token

https://github.com/ging/fi-ware-idm/wiki/Using-the-FI-LAB-instance#get-user-information-and-roles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-idm-ge/attachments/20130926/abc1f990/attachment.html>