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

kube-apiserver/audit-policy: document oauth token logging in 4.6+ #684

Conversation

sttts
Copy link
Contributor

@sttts sttts commented Mar 9, 2021

@sttts sttts force-pushed the sttts-secure-token-audit-logging branch 2 times, most recently from 78d8b1a to 303b14e Compare March 9, 2021 18:23
and by removing the exception for these resources in the `WriteRequestBodies` and `AllRequestBodies` policies.
New cluster deployed with 4.6 or later are identified through the `oauth-apiserver.openshift.io/secure-token-storage: true` annotation
on the `apiservers.config.openshift.io/v1` resource. Old cluster upgraded from 4.5 or older, don't have this annotation and hence do not
audit log `authaccesstokens` and `oauthauthorizetokens`, not even on metadata level as it is not know whether old, non-sha256 hashed tokens
Copy link
Contributor

@EmilyM1 EmilyM1 Mar 9, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not even on metadata level as it is not know whether old
should read not known

@@ -287,6 +311,11 @@ The profile translate like this:
# catch-all rule to log all other requests with request and response payloads
- level: RequestResponse
```

With secure OAuth storage in-place (compare "Logging of Token with Secure OAuth Storage" section) and
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

compare "Logging of Token with Secure OAuth Storage" section
should be
compared to

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it should be a reference. I write "see" instead.

@sttts sttts force-pushed the sttts-secure-token-audit-logging branch from 303b14e to b70991a Compare March 9, 2021 18:41
Copy link
Contributor

@EmilyM1 EmilyM1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 9, 2021
@mfojtik
Copy link
Contributor

mfojtik commented Mar 9, 2021

/approve

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: EmilyM1, mfojtik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 9, 2021
@openshift-merge-robot openshift-merge-robot merged commit 2d3d500 into openshift:master Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants