... and implement JWT auth

Expand RavenDB logic so that metadata entry "updated-by" is added on every save of the document

The value of this metadata property would be pulled from the current identity

• record exceptions better
• record input always
• record claims held by actor
• etc

1. Authentication will come from Claim in the token (research what is a standard claim for this)
2. Authorization will be managed within the application itself
3. Authorizer will check

• if the user is authenticated
• based on that identity, mandatorily required set of claims will be compared with claims in the database

When user logs in, we should be able to access to User without additional effort.

Add https://traefik.io/traefik/

... that will contain validation errors

When creating session, there are various options, like AggresiveCaching or Cluster-Wide transactions,
developer should be able to use them.
The less "magic" happening behind the scene, the better

https://github.com/App-vNext/Polly

For all distributed operations like working with a database, sending emails, etc.

In order to reuse this starting project as a basis for other projects, introduce parameterization for project name
and other elements

• project name
• logging details
• as few params as possible
• do not alter namespace and other "vanity" and "for completion" sake elements

This should clean up act phase

HttpResponseMessage SendAnonGett(string Url)
HttpResponseMessage SendAnonPost(string Url, string JsonPayload, Claim[] claims = null)
....

https://dev.to/kurtmkurtm/testing-net-core-apps-with-github-actions-3i76