Hi Torsten! If 'structured_scope' would become a generic field for application specific content, I believe an indicator for the type of content would be needed on the long run. That is what I meant my 'profile'. I hope this helps!
Thank you, Sascha Am Mo., 22. Apr. 2019 um 22:06 Uhr schrieb Torsten Lodderstedt <tors...@lodderstedt.net>: > > Hi Sascha, > > > Am 22.04.2019 um 20:34 schrieb Sascha Preibisch <saschapreibi...@gmail.com>: > > > > Thank you for the article, Torsten! > > my pleasure :-) > > > > > I like that 'scope' is out of the game for these kinds of authorizations. > > > > What I can see for the general use case is a required identifier > > within the 'structures_scope' document that identifies the profile it > > should be used for. > > What does profile mean in this context? > > best regards, > Torsten. > > > > Thank you, > > Sascha > > > > Am Sa., 20. Apr. 2019 um 11:21 Uhr schrieb Torsten Lodderstedt > > <tors...@lodderstedt.net>: > >> > >> Hi all, > >> > >> I just published an article about the subject at: > >> https://medium.com/oauth-2/transaction-authorization-or-why-we-need-to-re-think-oauth-scopes-2326e2038948 > >> > >> I look forward to getting your feedback. > >> > >> kind regards, > >> Torsten. > >> _______________________________________________ > >> OAuth mailing list > >> OAuth@ietf.org > >> https://www.ietf.org/mailman/listinfo/oauth _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
