Security
Every post in this series has described how Dawnshard works in some detail. Identity, profiles, RBAC, field-level permissions, business rules, realtime notifications scoped to what each profile is allowed to see. Security is woven through all of it. This post covers the security implementation.
The security architecture
Nice try, bro.
There is a real security implementation underneath Dawnshard and it is not trivial. We are simply not going to publish a map of it. Obscurity is not the model, but there is also no good reason to hand anyone a detailed breakdown of how authentication, token management, and session handling work in the specific application that runs Plan.Make.Trace.
The architecture exists. It is layered and consistent with everything described in the preceding posts. That is enough.
What's next
That is the Dawnshard foundation. The next post starts on Plan.Make.Trace itself.
Liked this post? Tap the heart to let us know.
Get early access
Be the first to hear about early access, roadmap updates, and exclusive early adopter pricing.
Join the early access list