{"full_name":"doorkeeper-gem/doorkeeper","owner":"doorkeeper-gem","name":"doorkeeper","shard":"1","url":"https://github.com/doorkeeper-gem/doorkeeper","description":"Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape.","homepage":"https://doorkeeper.gitbook.io/guides/","topics":["doorkeeper","oauth","oauth2-provider","oauth2-server","ruby-on-rails","grape","authorization","oauth2","authentication","identity"],"tag_pages":["authentication","authorization","identity","oauth","oauth2","ruby-on-rails"],"language":"Ruby","license":"MIT","avatar":"https://avatars.githubusercontent.com/u/7275750?v=4","created_at":"2011-11-18T13:02:01Z","pushed_at":"2026-11-14T12:18:52Z","metrics":{"stars":5541,"forks":1084,"watchers":98,"issues":930,"prs":1059,"releases":83,"issues_open":12,"issues_closed":918,"prs_open":16,"prs_closed":248,"prs_merged":795,"discussions":3},"growth":{"day":{"stars":0,"forks":0,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[5536,5537,5538,5539,5540,5541,5541],"forks":[1082,1084,1084,1084,1084,1084,1084],"watchers":[null,98,98,98,98,98,98],"issues_open":[null,12,12,12,11,11,12],"prs_open":[null,14,13,13,12,16,16]},"boards":{},"same_owner":[],"issues":[{"number":1600,"title":"Is there a way to store Doorkeeper::AccessToken data inside Doorkeeper::JWT (and not use db-backed tokens)?","comments":12,"created_at":"2022-11-08T15:52:29Z"},{"number":1678,"title":"Always requiring `redirect_uri` is not compliant to RFC 6749","comments":6,"created_at":"2023-11-22T14:09:08Z"},{"number":1948,"title":"Persist per-client token endpoint authentication methods on `oauth_applications`","comments":4,"created_at":"2026-09-20T08:55:24Z"},{"number":1977,"title":"Support for OAuth 2.0 Refresh Token and Authorization Expiration","comments":3,"created_at":"2026-10-24T04:26:50Z"},{"number":1719,"title":"Refresh Tokens as-implemented are susceptible to Refresh Token Reuse Attacks","comments":3,"created_at":"2024-07-25T18:15:46Z"},{"number":1675,"title":"Better support for credential rotation","comments":2,"created_at":"2023-10-25T20:58:21Z"},{"number":1971,"title":"Allow issuer to be resolved per request, and iss (RFC 9207) to be enabled per application","comments":1,"created_at":"2026-10-07T03:26:40Z"},{"number":1655,"title":"Support OAuth DPoP","comments":1,"created_at":"2023-04-25T16:33:02Z"}],"discussions":[{"number":1782,"title":"Support for OAuth 2.0 Dynamic Client Registration Protocol (RFC 7591) for OpenAI ChatGPT Connectors","comments":1,"category":"Ideas","created_at":"2025-11-15T21:14:46Z"},{"number":1763,"title":"Using redis instead of DB to verify access token","comments":2,"category":"Ideas","created_at":"2025-02-04T10:12:57Z"},{"number":1753,"title":"Disallowing HTTP query parameters for client_id/client_secret with authorization_code grant_type","comments":0,"category":"Q&A","created_at":"2024-12-02T13:52:00Z"}],"latest_release":{"name":"v5.9.9","tag":"v5.9.9","published_at":"2026-09-24T13:10:20Z","body":"- Fix: `AuthorizedApplicationsController` now answers `401 Unauthorized` instead of running with a `nil` resource owner, which listed and revoked every token that has no resource owner — the ones the client credentials flow issues. Affected host applications are those whose `resource_owner_authenticator` answers `nil` without halting the request itself; the generated initializer's example redirects and is not affected.\r\n- Fix: `AuthorizationsController#destroy` now validates the client and redirect URI before producing the deny response, and renders — never redirects — when validation fails. Previously the deny path performed no OAuth-layer validation at all, allowing an open redirect to an attacker-controlled origin with the OAuth `state` attached. Also reject unregistered `response_type` values on the authorization endpoint rather than resolving them through the `constantize` fallback.\r\n- Fix: refuse redirect URIs with a script scheme (`javascript`, `vbscript`, `data`) both when an application is registered and at authorization time, regardless of `forbid_redirect_uri`. Such a URI is never a legitimate redirection endpoint, and with `response_mode=form_post` it became the action of the auto-submitting form the authorization server renders on its own origin. Already stored records with such a URI are now refused with `invalid_redirect_uri` before the consent screen is shown.\r\n- [#1938] Fix: a request body ActionDispatch cannot parse (malformed JSON under a JSON content type, say) no longer raises `ActionDispatch::Http::Parameters::ParseError` out of `Doorkeeper::OAuth::Token.from_request` and `doorkeeper_token`. Since 5.9.7 the RFC 6750 §2 multi-method check read the body on every request, so such a request raised even when it carried a valid Bearer header. The body is now treated as carrying no token, the same way ActionDispatch's own `#filtered_parameters` treats that error.\r\n","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}