mdnfiras commented on issue #12640:
URL: https://github.com/apache/apisix/issues/12640#issuecomment-3351502283
in our case, we route the dashboard requests through apisix gateway and we
use `openid-connect` plugin to login to dashboard, and a custom plugin to
extract the user email address from the `x-userinfo` header (which was set by
the `openid-connect` plugin), and we save the email in a new header (i.e
`X-User-Email`). we rely on this new header to identify the user.
other authentication plugins like `key-auth` will end up setting
`X-Credential-Identifier` and `X-Consumer-Username`, so these are other headers
that can identify the user.
so if the audit logs feature allows the user to chose which request header
to be used as identity, then the user can:
* ensure that header exists (i.e by routing the dashboard requests through
apisix gateway then using some plugins),
* then set the header name in the apisix audit logs config to identify the
user.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
