IAM Logs
Sales staff enter business customers (e-mail, company) in the CRM; private and business customers register themselves in the self-service (name, password, e-mail, consent); both sources feed one user object in the IdP (name, password, e-mail, company).
* Two writers, one IdP use...
Q A sales employee records a new business customer, anna@firm.ch of Firm Ltd, in the CRM. Anna registe...
Look the user up in the IdP by e-mail, find Anna's existing account and only add the company to it; it must not create a second user and must not touch her password.
Walk through it the way the create flow does:
Capture: the new Customer (e-mail, company) is saved in the CRM.
Se...
Q What distinguishes regular, potentially irregular and irregular cases in a life-cycle state table, a...
Regular cases are expected situations with a defined action and are processed automatically; potentially irregular cases are those where a machine cannot decide from the current data whether something is wrong, such as temporary intermediate states or situations needing manual in...
Q What is a life-cycle process (LCP) in IAM, and why is CRUD its basic skeleton?
A life-cycle process manages one information object, such as an account, a password, a consent or a customer, from its creation through its changes to its deletion, so at its core it consists of create, update and delete operations (CRUD).
Every piece of identity data is born, ch...
Q A business customer tells sales that her e-mail address changes from old@firm.ch to new@firm.ch. Why...
Because the e-mail is the key that links CRM customer and IdP user, the user can only be found under the old address; the update must look it up with the old value and then overwrite it, which is why the model assumes the CRM keeps a change history.
The update flow branches on ex...
Q Classify these webshop situations as regular, potentially irregular or irregular: (a) an IdP user wi...
(a) is regular, a private customer who registered in the self-service; (b) is irregular, a company can only come from a CRM customer, so it is reported as an error; (c) is potentially irregular, most likely the sync has not run yet, so it is reported as a warning.
The reasoning i...
Q How do you work out which life-cycle processes a system landscape needs? Apply it to the webshop wit...
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...