oauth2Provider properties listed as optional but are mandatory

[macMikey]

here's the jwt document for google for web apps here's the jwt document for google for service accounts for web apps, the following fields are mandatory (but the netkit documentation says they're optional)

• response_type isn't mentioned in the netkit docs, but it's mandatory
• scope (no mention for google - but it's mandatory for both web apps and service accounts)

[e-marchand]

response_type seems to be set as "code" , because it cannot be changed for the moment, I think it must not be documented in this case (but maybe I do not read enought code) https://github.com/4d/4D-NetKit/blob/a77462e4704ec889fe8eee884e735fe8232b57db/Project/Sources/Classes/OAuth2Provider.4dm#L876

--

scope is not mandatory in Oauth2 protocol, it depend on api you use, it could even be ignored by server according to your right the server must choose a default one (as RFC say)

maybe doc could add mention when it is needed

[macMikey]

right. it's different, depending on the provider. rather than just changing the docs and issuing a PR, i wanted to throw out an issue, first, to discuss. what i would suggest is that:

• we add a column to show the differences between different consumers.
• we sort the properties alphabetically in the list.
• rephrase some of the descriptions to be more generic for consumers OR
• reorg some of the docs by consumer/use case, because service accounts, for example, are handled differently than user accounts, and google is different from ms
• consider using the wiki functionality in github for the documentation to make the readme less verbose