Solution to tag along authentication information for call flows, e.g. JWT

[stolsvik]

When a user initiates an order or similar, one might want to not only validate the authentication information at the entry point, but also at the "OrderService" which actually enters the order into the database. Also, it would be of interest to store this information along with the order for auditing purposes, so that it was possible at a later time to point to the specific login that caused the order to be entered.

The authentication could be either the user that himself logged in and performed the order, or a service worker that acted "on behalf of" the user. Both types of authentication information could be of interest to validate (and store) at the "OrderService" too.

Should this be a "tack on" solution using Mats' TraceProperties, or should it be a fundamental feature of the Mats API?

Handle multiple authentication types, e.g. SAML and JWT?