I have found that I had to put a scope encoding format into my database for each audience definition. Just saying that the scope is CBOR is not going to be sufficient, just like saying that it is a text string is not enough.
For the text string side you have: * It is a text string * It is a text string with space separated values * It is a text string with space separated values and each value has an underscore which separates operation and resource (MQTT) On the binary side you have: * The proposal from Carsten that has not get adopted anywhere yet. * The group communication format (roughly based on the above format) There is a question about how all of the binary values are going to work if you do a JSON encoded request rather than a CBOR encoded request. At the moment, I am assuming that the binary value is encoded (in CBOR) and then base64url encoded and placed in the JSON. I am not sure if people are going to want to define this as being native JSON instead depending on how the fields of the binary format are encoded. Given all of this, I don’t know if adding something to the framework is going to be generally useful or not. So much of what a scope looks like is going to be application dependent. With any luck we are going to be able to get a good set of scope definitions at some point in the near future and can produce a survey document. I am not holding my breath on this yet. Jim From: Francesca Palombini <francesca.palomb...@ericsson.com> Sent: Sunday, February 23, 2020 11:55 PM To: Mike Jones <michael.jo...@microsoft.com>; Jim Schaad <i...@augustcellars.com>; 'Seitz Ludwig' <ludwig.se...@combitech.se> Cc: 'Ace Wg' <ace@ietf.org> Subject: Re: [EXTERNAL] RE: Access token question Thanks all! Section 8.13 of the framework is exactly what I was looking for, I don’t know how I did not see it. A bit surprised there is no text referencing it in the framework itself. Also, about the “scope” claim registration: the claim description and the specification document give 2 different pointers. The claim description ref points to the description for JWT (JSON string etc), I think this should be adapted to using CBOR (writing a section in the ACE framework, which could then reference both pointers). Also minor, I would add the precise section of 6749 we should look at, which I assume is 3.3. Francesca From: Mike Jones <michael.jo...@microsoft.com <mailto:michael.jo...@microsoft.com> > Date: Friday, 21 February 2020 at 19:45 To: Jim Schaad <i...@augustcellars.com <mailto:i...@augustcellars.com> >, Francesca Palombini <francesca.palomb...@ericsson.com>, 'Seitz Ludwig' <ludwig.se...@combitech.se <mailto:ludwig.se...@combitech.se> > Cc: Ace Wg <ace@ietf.org <mailto:ace@ietf.org> > Subject: RE: [EXTERNAL] RE: Access token question And https://tools.ietf.org/html/rfc8693#section-7.4, which registers “scope” at https://www.iana.org/assignments/jwt/jwt.xhtml. -- Mike From: Jim Schaad <i...@augustcellars.com <mailto:i...@augustcellars.com> > Sent: Friday, February 21, 2020 9:15 AM To: 'Francesca Palombini' <francesca.palomb...@ericsson.com <mailto:francesca.palomb...@ericsson.com> >; 'Seitz Ludwig' <ludwig.se...@combitech.se <mailto:ludwig.se...@combitech.se> >; Mike Jones <michael.jo...@microsoft.com <mailto:michael.jo...@microsoft.com> > Cc: 'Ace Wg' <ace@ietf.org <mailto:ace@ietf.org> > Subject: [EXTERNAL] RE: Access token question You are missing something https://tools.ietf.org/html/draft-ietf-ace-oauth-authz-33#section-8.13 defined here From: Francesca Palombini <francesca.palomb...@ericsson.com <mailto:francesca.palomb...@ericsson.com> > Sent: Friday, February 21, 2020 4:37 AM To: Seitz Ludwig <ludwig.se...@combitech.se <mailto:ludwig.se...@combitech.se> >; Mike Jones <michael.jo...@microsoft.com <mailto:michael.jo...@microsoft.com> >; Jim Schaad <i...@augustcellars.com <mailto:i...@augustcellars.com> > Cc: Ace Wg <ace@ietf.org <mailto:ace@ietf.org> > Subject: Access token question Hi, Quick question regarding access token and scope. I know that “scope” semantics is left to the application to define, but in general I would expect to include there some information about resource and method/operations allowed on that resource. Please correct me if any of this is not exact. It was my understanding that “scope” (or more precisely the “scope” value) defined for the Client-AS request and response should be included in the access token as well. Checking in CWT, there is no such “scope” claim defined. “aud” claim is indeed defined for the CWT, but that should correspond to “aud” parameter in the ACE request/response. So where do I put the exact resource and operations in the access token? What am I missing? Francesca
_______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
