Debugging OAuth issues is time-consuming. We should have a dashboard which lists errors on the OAuth channel by error code and client ID, and shows top error codes and top client IDs.
This will probably require improving the extension code as currently it doesn't log error details.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Log additional error details | mediawiki/extensions/OAuth | master | +261 -73 | |
| Normalize logging of nonce error | mediawiki/extensions/OAuth | master | +2 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Tgr | T332663 Create an OAuth error dashboard | |||
| Open | None | T188848 All OAuth logs should include the consumer key |
Change 907976 had a related patch set uploaded (by Gergő Tisza; author: Gergő Tisza):
[mediawiki/extensions/OAuth@master] Normalize logging of nonce error
Change 907976 merged by jenkins-bot:
[mediawiki/extensions/OAuth@master] Normalize logging of nonce error
Change 908363 had a related patch set uploaded (by Gergő Tisza; author: Gergő Tisza):
[mediawiki/extensions/OAuth@master] Log additional error details
Change 908363 merged by jenkins-bot:
[mediawiki/extensions/OAuth@master] Log additional error details
@Tgr do you need a real use case to test this new dashboard? I'm having a hard time to implement chunk upload in my tool as I always face a "mwoauth-invalid-authorization / The authorization headers in your request are not valid: Invalid signature".
https://logstash.wikimedia.org/app/dashboards#/view/1e16dc40-e07a-11ed-ae74-e713b6900c9a - feedback welcome.
What is your consumer key / client key?
Is the logstash instance accessible with a developer account? I can't login.
My consumer key is 8acb020c652621d785c8024ca2bb9a94 but I managed to solve my issue meanwhile. I was including params in the base signature string for a multipart request. The "invalid signature" error returned by the API helped me a lot to narrow the issue.