-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Provide client info in argocd server errors #20388
Comments
In terms of information I think I want about the token itself, it's roughly:
Where each of them could be truncated to probably 64 chars (anyone using more than 64 for most of those fields is being evil).
(This is, of course, in addition to including the client IP address, and probably port.) |
We have to be careful with logging a potentially sensitive info like tokens, but ip seems to be fine. |
I'm reading logs and am trying to figure out who's flooding them with error messages. All I have is the logs, nothing else, and the logs are useless. |
Would logging a token sha be sufficient? |
dunno, what can i do with that? |
You can store a table mapping a token sha to users for example. |
Though other fields like issuer and expiration date are probably fine. But I also don't know if that's enough. |
This message:
from
argo-cd/util/oidc/oidc.go
Line 378 in e80de49
isn't actionable.
At the very least, it needs to include a client ip. If it knows about a "user" or some similar thing, it should include that too.
At the same time, there's a thing in the verify side which hoped that the go oidc provider would do something, and that pr was closed, so the comment should be removed:
argo-cd/util/oidc/provider.go
Lines 133 to 135 in e80de49
The text was updated successfully, but these errors were encountered: