Proposal to describe OAuth2 flows

[leoniv]

Hello everyone!

Here is proposal how to describe OAuth2 a bit more precisely. I encountered in inability to describe the client credentials flow and then I looked through the code and made up with such solution. It's not pretty well, but it should work.

[adamw]

Thank - these changes look good! MiMA seems to pass without problems?

One idea that might improve the discrimination of flows is using an attribute on the input returned by authorizationCodeFlow etc. - we could define a dedicated datatype which would hold the scope types, define an AttributeKey, set it in the *flow methods, and read in the docs interpreter.

We use attributes in a similar way e.g. to support the title property:

tapir/core/src/main/scala/sttp/tapir/Schema.scala

Line 332 in 978dca6

val Attribute: AttributeKey[Title] = new AttributeKey[Title]("sttp.tapir.Schema.Title")

Wdyt?

[leoniv]

One idea that might improve the discrimination of flows is using an attribute on the input returned by authorizationCodeFlow etc. - we could define a dedicated datatype which would hold the scope types, define an AttributeKey, set it in the *flow methods, and read in the docs interpreter.

This idea is much better, take a look pleas.

[adamw]

Thanks! :)