Scopes and Application Registration

Radomir reports in Invalid scope when re-authorizing for expire that "The requested scope is invalid, unknown, or malformed." Perhaps the problem is that we're reusing the client secret from a client who was registered for the read scope and now we're trying to access read and write scope.

Workaround and test: delete the two *.secret files before expiring toots. If that works, then perhaps that's what we should do: re-register the application before attempting to authorize.

Tags: Closed

Reopen issue


This wiki uses a variant of Markdown.

To save this page you must answer this question:

Please write "new issue" into the field below.