as far as I remember right, it's allowed to pass the token as query parameter. But per spec it's a "MAY" so it's optional. And, at least in 9.0.5, the version we implemented the idp originally, it hasn't been implemented and needed to be added. Anyway it was a larger project implementing all the needed "MAY" features with OAuth and especially OIDC. So if there is no real need for the optional implementations, I'd suggest to stick with the available options. Just don't use implicit flow for security reasons.
------------------------------
Jens Petersen
------------------------------
Original Message:
Sent: Tue August 04, 2020 07:18 PM
From: Sylvain Gilbert
Subject: OAuth , Requesting protected resource with access token on query parameter
As per oauth spec, have you validated that passing an oauth token as query parameter is a recommended practice ? I believe the specs describes the inherent risks associated with such approach and this why this is no no approach.
Then I guess next question in line is why you don't let mobile app negotiate for itself it's own token ? You can share a bit more of your use case ?
Authorization grant code flow is one example of way to go with mobile apps that works ok.
------------------------------
Sylvain Gilbert
------------------------------
Original Message:
Sent: Mon July 27, 2020 06:32 AM
From: Piyush Agrawal
Subject: OAuth , Requesting protected resource with access token on query parameter
Is there anyone who has tried this?
------------------------------
Piyush Agrawal