7 Commits (bfa9ce4308ca897711eb1b822bd5f0e31bbef31d)

Author	SHA1	Message	Date
Tim St. Clair	a5de309ee2	Implement audit policy logic	2017-05-25 07:38:07 -07:00
Dr. Stefan Schimanski	0b5bcb0219	audit: add audit event to the context and fill in handlers	2017-05-23 11:20:14 +02:00
Mike Danese	a05c3c0efd	autogenerated	2017-04-14 10:40:57 -07:00
Kubernetes Submit Queue	67f2a7cc00	Merge pull request #43888 from liggitt/unsecured-port-user ... Automatic merge from submit-queue (batch tested with PRs 43545, 44293, 44221, 43888) Avoid nil user special-casing in unsecured endpoint The unsecured handler currently adds no `user.Info` to the request context. That means that anything that tries to authorize actions in the API server currently has to special case nil users to ensure the unsecured localhost endpoint remains capable of performing all actions. This PR changes the unsecured localhost endpoint to be treated as a privileged user internally, so that no special casing is required by code inside the authentication layer I'm not particularly attached to the username. It doesn't bother me for it to have a slightly uncomfortable sounding name.	2017-04-11 12:18:24 -07:00
deads2k	b73cddb227	only log stacks on server errors	2017-04-10 07:57:43 -04:00
Jordan Liggitt	5d839d0d0b	Avoid nil user special-casing in unsecured endpoint	2017-03-31 13:28:59 -04:00
deads2k	cd29754680	move legacy insecure options out of the main flow	2017-03-27 14:07:54 -04:00