We need to wait until Chef 11, when we can make a break to change to 1.1, because this relies on the server side supporting 1.1 to work correctly.
This release changes the default protocol and is a breaking change for users of the prior protocol version. If you use this release you need to ensure your servers are upgraded first so they support the new protocol. Further work on protocol negotiation is planned.
adding issue tracker url to README.rdoc
…do not contain 'algorithm': default to 'sha1' if it's not there.
for some totally weird reason, starting chef-server via the rackup file causes mixlib/authentication to get loaded twice. This causes a superclass mismatch when inheriting from Struct.new. Since we aren't adding any behavior to the struct, we can just assign it to a constant and get the same results.
...so that malformed requests are caught before we try to use any of their headers
* Can now create the signature verification object w/ the request and then access values computed by the HTTPAuthenticationRequest object. * created a #authenticate_reqest method that can be used when signature verification is initialized w/ the request * #authenticate_user_request works as before
higher layers will use this to inform the user if they got a 401 b/c of incorrect clock on the client