Statping: response_type parameter seems to be missing in custom oauth settings

[hurriyetgiray-ping]

Using Statping 0.90.56 which has Oauth as beta. Used custom oauth but getting error
http://localhost:8080/oauth/custom?error=invalid_request&error_description=No%20value%20supplied%20for%20required%20parameter:%20response_type%20(Correlation%20ID:%..... )

It seems the error is due to the missing request_type parameter in the request to authorization server. It is as follows:
https://<custom oauth.com auth endpoint>?client_id=<xxxxx-xxxxx-xxxxx xxx>&redirect_uri=http://localhost:8080/oauth/custom

When I add _?request_type=token id_token_ via curl or POST as below, the login is directed to the authorization server as I would expect
https://<custom oauth.com auth endpoint_>?client_id=<xxxxx-xxxxx-xxxxx xxx>&request_type=token id_token&redirect_uri=http://localhost:8080/oauth/custom

I think request_type is required in the oauth2 spec, but just wondering if it is left out for a reason and that I am missing something.

https://tools.ietf.org/html/rfc6749 - 3.1.1 Response_Type

[hunterlong]

Hey @hurriyetgiray-ping , thanks for this issue. OAuth is still in beta, but I've had good results with Github and Slack, Google and Custom i'm stilling trying to confirm everything. I'll be working on this.

[quentinus95]

I can confirm that I get the following kind of errors using Custom:

error=invalid_request
error_description=Missing parameter: response_type

[github-actions[bot]]

This issue hasn't had any updates in a while. If this is still a problem, please create a new issue.

[hurriyetgiray-ping]

It is still a problem, so I had to find a workaround. I am now using another app for oauth authentication and bypassing statping's native login.

I am expecting https://github.com/statping/statping/issues/605 will address this.

[github-actions[bot]]

This issue hasn't had any updates in a while. If this is still a problem, please create a new issue.