Torsten,
I think that works in most cases if you look at it that way.
It is just that elements such as 'iban' are practically unknown here
in Canada for example. This means, there needs to be a differentiator
that tells a client that one payment may be of type 'payment_eu' and
in the other case '
> Am 25.04.2019 um 17:03 schrieb George Fletcher :
>
> A couple of thoughts...
>
> 1. It doesn't feel like these are scopes (at least not as scope is defined by
> RFC 6749). It feels like they are more transaction requirements.
What’s the difference? In my opinion, if you authorize a transact
A couple of thoughts...
1. It doesn't feel like these are scopes (at least not as scope is
defined by RFC 6749). It feels like they are more transaction requirements.
2. The schemas are going to be very ecosystem specific, correct?
On 4/24/19 1:08 PM, Torsten Lodderstedt wrote:
Hi Sascha,
I
Hi Torsten and others,
I just read your blog - having “we need to re-think OAuth scopes” in the title
immediately drew my attention.
I find this interesting since I’m struggling with the concept of scopes from
time-to-time.
I’ll have to read the blog a few times more to get a good understanding,
