argoproj / argoproj/argo-workflows

Email in Argo Server audit Log and GDPR

Open
#9,808 6 comments 1 reaction 0 assignees View on GitHub
area/server type/security
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 20h
Merged PRs (30d)
138

Description

# Summary

Currently [argo server gatekeeper will log the email in an audit log](https://github.com/argoproj/argo-workflows/blob/d0cfc6d10b11d9977007bb14373e699e604c1b74/server/auth/gatekeeper.go#L314). This is not great because email is personally identifiable information in Europe and is subject to GDPR.

I suggest being able to choose what is logged/what is not logged through the argo server configmap. For example custom claims, groups etc.

# Use Cases

- In countries with GDPR or other personal information legislation explicitly disabling email logging
- More granular auditing. For example logging which OIDC group the user belongs to.

---

**Message from the maintainers**:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Contributor guide

Open the contributing guide

Research direction

Start at server/auth/gatekeeper.go around line 314 and review how Argo Server audit logging and the ConfigMap relate. Clarify the configurable audit fields, including email, custom claims, and groups; done means users can select which identity data is logged, including disabling email logging.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.