A BRMS and authorization management
As I quickly mentioned in the previous chapter, there is a functional domain in the DemoEditor sample information system where an externalized business rules engine would be interesting, and this domain is one of authorization. Before explaining the need to clarify the semantics of the “rights” business domain, examine the main paradigms to implement authorization in software applications, and also explain one of the standards associated with this function, which decomposes very well the different responsibilities it entails.
The semantics of identity and authorization management
As explained in Chapter 9, semantics is the foundation of all things in architecture, and we will clarify the terms we use for certain concepts in order to not incorrectly define the business domain model. Thus, it is important to clearly define the different subdomains of Identity and Authorization Management (IAM) and how we name things inside of them...
