{"push_id":692606361,"size":1,"distinct_size":1,"ref":"refs/heads/authframework","head":"1c83a42f1bb8d50bc4a7bdf37edfdf4abd7c138a","before":"e4fff5f5ea259fbbe6247910ecff46d6b9a3d43d","commits":[{"sha":"1c83a42f1bb8d50bc4a7bdf37edfdf4abd7c138a","author":{"email":"f562fcb2a0b898bf0be1afc867ea92325d8f825f@redhat.com","name":"Nalin Dahyabhai"},"message":"Add a client-daemon authentication framework\n\nAdd the basic framework for requiring clients to authenticate to the\ndaemon when issuing requests to it.  This is mainly plumbing and wiring\nin the logic in both the client and the server.\n\nThe client and server both contain module-local lists of implementations\nof authentication schemes which those implementations will add\nthemselves to at initialization time.  The list on clients is a set of\nAuthResponders which is indexed in the client map by the authentication\nschemes that they implement.  The list on servers contains is a set of\nAuthenticators.\n\nThe client will call its AuthResponders if it receives a 401 error, and\nif any of them signal that the client should try again after that\nAuthResponder has had a chance to modify the request, it will do so.\n\nThe server will call its Authenticators Startup methods at startup, and\neither their GetChallenge methods or CheckResponse methods for each\nrequest, depending on whether or not the request includes authorization\nheaders.  If CheckResponse indicates that the client's identity has been\nverified, information about the authenticated user will be added to the\nrequest structure as a shared value so that it can be used by handlers.\n\nSigned-off-by: Nalin Dahyabhai <nalin@redhat.com>","distinct":true,"url":"https://api.github.com/repos/nalind/docker/commits/1c83a42f1bb8d50bc4a7bdf37edfdf4abd7c138a"}]}