add filter for logging principal of incoming requests

[djibodu]

What

Add filter to locally log principal of user sending incoming request.
Example log: [2025-04-01 15:37:05,444] INFO [6c95ca51-f2ec-497b-ac48-d27eea303cdf] Resource association log - (Principal, schemaHash): (u-dummy, a236344d3b2bbe2cc09439868bfc7168) (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:2646)

Checklist

• Contains customer facing changes? Including API/behavior changes
• Is this change gated behind feature flag(s)?
  • List the LD flags needed to be set to enable this change
• Did you add sufficient unit test and/or integration test coverage for this PR?
  • If not, please explain why it is not required
• Does this change require modifying existing system tests or adding new system tests?
  • If so, include tracking information for the system test changes

References

JIRA:

Test & Review

Open questions / Follow-ups

[confluent-cla-assistant]

🎉 All Contributor License Agreements have been signed. Ready to merge.
_{Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.}

[MSeal]

Can we put an example log message for this PR? I'd like to see what the message looks like to review for feedback as well if possible. Also that's a lot of SonarCube alerts in this repo, hoping you have a techdebt item to resolve or ignore that particular empty body rule for the repo?

[MSeal]

How does this pull out the user_id field from the REQUEST types? I am not super familiar with this code base to know what this does implicitly.

[djibodu]

all requests that come into SR will pass through this request filter, which will set the principal user (unique identifier for the request sender) in a principalContext. this is needed because the logs are populated at the service level, not at the request level - so we keep it in a principalContext which can be read when the actual CRUD SR calls happen. I have also added a sample log to the PR description - let me know if you want it reformatted another way

[MSeal]

Got it, yeah I wasn't sure which id or reference the principalContext would use by default. This and the example log message clarify that, thanks!

[sonarqube-confluent]

• 49.70% Coverage on New Code (is less than 80.00%)

Analysis Details

227 Issues

• 8 Bugs
• 1 Vulnerability
• 218 Code Smells

Coverage and Duplications

• 49.70% Coverage (73.40% Estimated after merge)
• No duplication information (2.20% Estimated after merge)

Project ID: schema-registry

View in SonarQube