[02:47:27] [telegram] Anyone good at OAuth? [02:47:28] [telegram] I am POSTing to https://www.mediawiki.org/w/rest.php/oauth2/access_token with [02:47:29] [telegram] {"grant_type":"authorization_code","code":"code","client_id":"c2cf922accd9d840217c547c01ce6fd8","client_secret":"my secret","redirect_uri":"http://localhost:4141/lol"} [02:47:30] [telegram] I have also tried to send the same as multipart instead of as a json. I keep receiving a 400 with [02:47:37] [telegram] {"error":"invalid_request","error_description":"The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.","hint":"Check the `grant_type` parameter","message":"The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed."} [02:47:39] [telegram] What am I missing? [03:05:06] [telegram] well, since Postman's OAuth 2.0 tool managed to get through and give me the access token I did miss something after all, but it would still be interesting to hear what exactly [03:55:10] [telegram] I'm completely beat today, but myself and a few others have managed to get oauth v2 fully working with mediawiki after ao Bugfix recently. Please remind me to point you the best docs and help you troubleshoot the issue tommorow or after. (re @Thecladis: Anyone good at OAuth? [03:55:11] [telegram] I am POSTing to https://www.mediawiki.org/w/rest.php/oauth2/access_token with [03:55:13] [telegram] {"grant_type":"authorization_code","code":"code","client_id":"c2cf922accd9d840217c547c01ce6fd8","client_secret":"my secret","redirect_uri":"http://localhost:4141/lol"} [03:55:14] [telegram] I have also tried to send the same as multipart instead of as a json. I keep receiving a 400 with [03:55:21] [telegram] {"error":"invalid_request","error_description":"The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.","hint":"Check the `grant_type` parameter","message":"The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed."}) [07:15:50] [telegram] is there any decision about the Hackathon? [07:33:41] [telegram] Lots of people are wondering, including myself. I'm not involved in organization at all, but I'm certain that the WMF and the organizers on the ground in Albania are discussing it actively and that when reach a decision, they'll communicate it as soon as they can. [07:48:45] chicocvenancio: you should probably file a bug about that [07:49:05] the REST API doesn't support multipart but there should be a more useful error message about that [07:52:05] [telegram] Oh, but still when using JSON something was missed too and I would love to know what (re @wmtelegram_bot: [irc] the REST API doesn't support multipart but there should be a more useful error message about that) [07:53:25] [telegram] Thanks, I will later. I do not have experience with OAuth elsewhere and I was just trying to follow https://www.mediawiki.org/wiki/OAuth/For_Developers manually (re @chicocvenancio: I'm completely beat today, but myself and a few others have managed to get oauth v2 fully working with mediawiki after ao Bugfix recently. Please remind me to point you the best docs and help you troubleshoot the issue tomm [07:56:40] Thecladis: yeah, that error message is not super helpful. Probably worth a bug report on its own. [12:44:02] [telegram] Makes sense. Will help with that later today. (re @wmtelegram_bot: [irc] Thecladis: yeah, that error message is not super helpful. Probably worth a bug report on its own.) [16:22:07] [telegram] According to emails, there will be a decision by middle of April, maybe earlier. (re @Galder: is there any decision about the Hackathon?) [18:46:21] [telegram] https://cutle.fish/blog/12-signs-youre-working-in-a-feature-factory [19:17:46] [telegram] Thats a nice one. Will casually drop this on a couple of peoples desks... :) (re @Daniel: https://cutle.fish/blog/12-signs-youre-working-in-a-feature-factory) [21:33:02] [telegram] so I have managed to get my access token manually by using url-encoded formdata (instead of json or multipart) and by having client id and secret as basic auth credentials)