Skip to content
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

Access logging to standard out #2

Closed
mlbiam opened this issue Nov 19, 2021 · 1 comment
Closed

Access logging to standard out #2

mlbiam opened this issue Nov 19, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@mlbiam
Copy link

mlbiam commented Nov 19, 2021

Currently the proxy supports audit logs in the same way that the API server does. this is duplicative and doesn't cover a major use case of tracking which user is accessing each URL. From a SIEM perspective, it would be good to support a simpler logging model as well that logs:

  1. timestamp
  2. URL
  3. User
  4. Authentication success or failure (ie did the token fail)

this can additionally log other events too such as inbound impersonation

@mlbiam mlbiam added the enhancement New feature or request label Nov 19, 2021
@mlbiam mlbiam self-assigned this Nov 19, 2021
@mlbiam mlbiam added this to the 1.0.0 milestone Nov 22, 2021
mlbiam referenced this issue in mlbiam/kube-oidc-proxy Nov 25, 2021
mlbiam referenced this issue in mlbiam/kube-oidc-proxy Nov 25, 2021
@mlbiam mlbiam closed this as completed Nov 25, 2021
@mlbiam mlbiam reopened this Dec 15, 2021
@mlbiam
Copy link
Author

mlbiam commented Dec 15, 2021

need to stop double logging the source ip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant