CIAM is a hot topic and a solution domain, but is it as clear and defined solution as it is sometimes thought of? Do the solution-models and functionalities provided by products and services meet the real business and technical requirements when they are not necessarily within same system or business-domains and have a lot of different stakeholders. How are different CIAM products' functionalities aligned with different organisational structures and processes, online-services, customer use-cases, regulational landscapes etc? What is needed to even start aligning CIAM-scoped -functionalities in siloed organisations with a lot of legacy and complex data-architecture? How to build a roadmap for such an organization and how to get the different stakeholders committed? Key takeaways: |
What is the relation between customer, business, technical, organizational and regulational requirements in a cross-cutting project like CIAM. What are the true challenges and what CIAM actually is from architectural perspective? - The requirements and promises placed on CIAM are scattered around business and technical and even contradictionary |