IAM Logs
Identify every information object that is created, changed and deleted on its own terms, give each its own LCP, and check that every attribute in every system belongs to exactly one of them; here that yields four LCPs: business customer, account, password and consent.
* Colour e...
Q A business customer ends the relationship and sales deletes her in the CRM. What happens to her IdP...
The deletion is propagated and the IdP user is deleted completely, with name, password, e-mail and company; if she later wants to shop as a private customer, she has to register again.
The delete flow is short: delete the Customer in the CRM, search the user in the IdP, delete th...
Q What life-cycle states can the IdP user pass through in the webshop scenario, and which events move...
Three states: no user, private user (no company, own password) and business user (with company); self-registration, CRM creation, CRM deletion, account deletion and updates move it between them.
* A state diagram makes every entry and exit of the object explicit, including the o...
Q What does the business-customer LCP manage, and which business event triggers each of its operations...
It creates, changes and deletes company customers in the CRM and propagates them to the IdP; the triggers are a signed contract (create), a change notice from the customer (update) and the customer ending the business relationship (delete), always carried out by sales staff.
O...
Q What does a system view (Systemdarstellung) of the business-customer LCP show, and what does the IdP...
It shows which systems and components take part and which function calls which: sales use CRM functions, the CRM calls an IdP sync job, and the job checks which action is needed, then updates an existing user or creates a new one with an initial password and writes the changes in...
Q Why must the business-customer LCP be coordinated with the account and password LCPs, and what is at...
Because the CRM, through sales, and the self-service, through the customer, both write into the same IdP user, an operation of one LCP can overwrite or delete the other's data; deciding which source owns which attribute, for example the company from the CRM and the password from...
Q Why is the password LCP subordinate to the account LCP, and what follows from that?
A password only exists as part of an account: it cannot be created before the account and must disappear with it, so every password operation runs inside the account's life cycle, even though it has its own triggers.
"Subordinate" (untergeordnet) means a strict dependency:
Creat...
Q How is the business-customer LCP drawn as a flowchart, and what does each flow look like?
One flow per operation (create, change, delete), each running from a start node through activities and yes/no decisions to an end node, with the actor optionally drawn on the left and the affected system on the right of each step.
* Each decision diamond is a branch the implemen...
Q Which representation of a life-cycle process suits which stakeholder, and why?
Management wants a compact overview of benefit and cost, developers want technical detail such as UML plus text and tables they can turn into tests, lawyers want text and permission tables covering data protection, consent and deletion, and project leads, architects and administr...
Q Why does consent get its own life-cycle process, and how does it interact with the other LCPs?
Consent (Einwilligung) to the processing of personal data is an object of its own that is given, changed and withdrawn independently of the account; because consent is the precondition for processing, the other LCPs may only process the customer's data while a valid consent exist...