OAuth2 Native Client type rfc 8252 paragraph 2 and 3

mikara89 — Wed, 22 Nov 2023 09:50:01 GMT

I don't see deference between those two clients types, except Web Client have M2M feature. I expect Native Client to have possibility to add redirect url with schema that is not http/https like not like "myapp://..." but like "com.example.myapp://..." that is explained in rfc 8252 paragraph 2 and 3, so we can use it in mobile devices.

Re: OAuth2 Native Client type rfc 8252 paragraph 2 and 3

mikara89 — Thu, 23 Nov 2023 10:38:13 GMT

After testing I figured out that I can use single slash ":/" instead of "://" and that is described in ietf 7.1(last two paragraphs) .So com.example.myapp:/callback is my redirect url that is acceptableby mobile app.

topic OAuth2 Native Client type rfc 8252 paragraph 2 and 3 in App Development

OAuth2 Native Client type rfc 8252 paragraph 2 and 3

Re: OAuth2 Native Client type rfc 8252 paragraph 2 and 3