-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rack::Auth::Digest is deprecated and will be removed in Rack 3.1 #2294
Comments
What's the upgrade path for someone using For grape this sounds like a breaking change either way. Upgrade to Rack 3.x, remove any code that breaks, major version bump. Thanks! |
The upgrade path should be using any modern auth mechanism instead. The fallback path should be using Basic Auth. The README already offers some alternatives: Use Doorkeeper, warden-oauth2 or rack-oauth2 for OAuth2 support.
The PR doesn't mention reasons why but:
I am assuming they're removing it because it should be removed.
Want me to make a PR? |
Yes please! |
It's completely insecure, unless you use it over TLS, in which case basic auth is simpler and just as secure. |
Removed by #2361. |
Nice work team! |
Closed via #2361 |
Rack 3.0 deprecated
Rack::Auth::Digest
and began warning that it would be removed in Rack 3.1.The main branch of rack removed
Rack::Auth::Digest
entirely on Sept. 10 2022.Grape requires
rack/auth/digest/md5
explicitly in v1.7.0 and appears to have done so for a long time because it's referenced in upgrading to >= 0.9.0. It's also mentioned in the README as a supported auth mechanism.Using
gem 'rack', github: 'rack/rack'
raises aLoadError
when starting a Grape app:I can successfully run the app after removing the require call for
rack/auth/digest/md5
inlib/grape.rb
, the method definition forhttp_digest
inlib/grape/middleware/auth/dsl.rb
and the call tohttp_digest
inlib/grape/middleware/auth/strategies.rb
.I'm happy to open a PR to completely remove support for digest auth from Grape but it's a major breaking change so I wanted to open a discussion before doing so in case there's a different course of action that's preferable.
The text was updated successfully, but these errors were encountered: