Skip to content
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

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

Open
stolsvik opened this issue Sep 1, 2019 · 0 comments
Labels
thoughts Issues describing some thoughts around a subject

Comments

@stolsvik
Copy link
Contributor

stolsvik commented Sep 1, 2019

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?

@stolsvik stolsvik transferred this issue from another repository Sep 27, 2021
@stolsvik stolsvik added the thoughts Issues describing some thoughts around a subject label Oct 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
thoughts Issues describing some thoughts around a subject
Projects
None yet
Development

No branches or pull requests

1 participant