Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
mikara89
Contributor II
Contributor II

OAuth2 Native Client type rfc 8252 paragraph 2 and 3

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. 

mikara89_0-1700646340065.png

 

Labels (1)
  • SaaS

1 Solution

Accepted Solutions
mikara89
Contributor II
Contributor II
Author

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.

View solution in original post

1 Reply
mikara89
Contributor II
Contributor II
Author

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.