[Openid-specs-native-apps] AppInfo endpoint

[John Bradley]

In the case of the appinfo endpoint it is controlled by the same entity as the AS.   OAuth doesn't restrict the token format, I don't know that we should.

What interoperability issue do you see.   I can see an argument for standardizing the access tokens when they are issued for external resources.   
On the other hand using the assertion flow gets around that to some extent.
be sent 
The reason that it is GET or POST is that some clients may not be able to place the token in a header to safely use GET,  OAuth allows the AT to the Protected resource in a POST body as an option.

John B.

On Sep 29, 2014, at 8:01 PM, Emily Xu <exu at vmware.com> wrote:

> Thanks for your reply John. For question number 1, I hope we can define some standard claims in access token for better interoperability. 
> 
> Another question: Section 7.2 says "To obtain application metadata information, the TA MAY make a GET or POST request to the AppInfo Endpoint.". Any reason we add POST request there?
> 
> Thanks,
> Emily
> 
> From: John Bradley <ve7jtb at ve7jtb.com>
> Date: Monday, September 29, 2014 12:03 PM
> To: Emily Xu <exu at vmware.com>
> Cc: "openid-specs-native-apps at lists.openid.net" <openid-specs-native-apps at lists.openid.net>
> Subject: Re: [Openid-specs-native-apps] AppInfo endpoint
> 
> Inline
> On Sep 29, 2014, at 1:23 PM, Emily Xu <exu at vmware.com> wrote:
> 
>> I have a couple of questions related to NAPPS AppInfo endpoint.
>> 
>> 1. In Section 7.2.1, it says "Access Token obtained from an OpenID Connect Authorization Request". I assume it means the access_token should contain "openid" in scope. Is it correct?
> 
> The format of access tokens issued by the Authorization endpoint for the AppInfo endpoint is unspecified, as the AppInfo endpoint and the AS are tightly related and the tokens are opaque to the client.
> 
> The Authorization request MUST have "openid" in the scopes requested.  It is however up to the AS to decide if that needs to be indicated in the access token.
> 
>> 
>> 2. In Section 7.2.2, it says
>>  "apps
>> REQUIRED (Array). One or more JSON objects containing claims about applications that the TA can provide tokens or web boot-stap uri for."
>> 
>> Any reason it must be "One or more" instead of "Zero or more"? If there is zero app authorized for this particular user, what the response should be?
> 
> OK Good point if there are no apps then it would be an empty array.   I suspect that was a hold over from the TA validating the bundleid directly as the TA woulden't have had much to do with zero apps.
> 
> I will make that change.
> 
> John B.
>> 
>> Thanks,
>> Emily
>> _______________________________________________
>> Openid-specs-native-apps mailing list
>> Openid-specs-native-apps at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-native-apps
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-native-apps/attachments/20140929/55e5c937/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4326 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-native-apps/attachments/20140929/55e5c937/attachment.p7s>