Infinite OAuth retry loop when refresh token is revoked

XMLWordPrintable

      When the OAuth refresh token is revoked server-side, Picard enters an infinite retry loop because the server returns invalid_request instead of invalid_grant, and the code only handled the latter.

      This prevents authenticated requests (releases with user-collections, collections) from everĀ  completing and consumes rate limit budget indefinitely until the application is restarted.

            Assignee:
            Zas
            Reporter:
            Zas
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                3.0.0b9
                2.14