| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
require_relative is significantly faster and should be used when available.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
| |
|
|
|
|
| |
It's possible that a request contains more than nine headers like "x_ops_authorization_n".
In this case headers will be sorted in the wrong way. The first will be "x_ops_authorization_1",
the second "x_ops_authorization_10" and so on. So that request signature transfered by parts in "x_ops_authorization_n" headers will be reconstructed in wrong way. So that authentication will fail.
|
| |
|
|
| |
Signed-off-by: Thom May <thom@may.lt>
|
| | |
|
| | |
|
| |
|
|
|
| |
...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
|
| |
|
