Practitioner thinking, from the people doing the work.

Abstract In modern platform engineering, tooling forms the backbone of system performance, security, and scalability. Despite this, many...

Control CIAM Resiliency with Hybrid Architecture This paper discusses Midships' design and implementation of a hybrid Customer Identity & Access Management (CIAM) architecture. The hybrid solution is proposed to address concerns about shifting resiliency responsibilities entirely to Software as a Service (SaaS) CIAM services, such as ID Cloud. The hybrid architecture utilises an on-premise CIAM deployment as a standby in the event that ID Cloud is unavailable. Where ID Cloud

The Reality Check Too often, CIAM journeys are built one channel at a time. Mobile login here, web onboarding there, branch-only password resets. It works at first—until it doesn’t. As each channel evolves, it throws new demands at CIAM. You patch, you duplicate, you tech-debt your way forward. Before long, your identity layer becomes a spaghetti mess. This article is your escape route. We’re laying out a definitive list of IAM journeys and features that a retail bank CIAM

Introduction For large enterprises, a robust CIAM (Customer Identity and Access Management) system is expected to serve as a centralised service within the enterprise architecture – supporting multiple channels and regions seamlessly. By functioning as a centralised identity provider, CIAM enables customers to use a single set of credentials across various digital channels, eliminating the hassle of creating and remembering multiple channel-specific logins. Throughout Midshi

Preface At Midships, we take pride in our originality, not merely conforming to the norm. Our dedicated team devotes considerable time to comprehensively grasp the distinct challenges faced by our clients and their customers, continually seeking enhancements. This necessitates the abandonment of entrenched biases and the dismissal of the idea that the way things are commonly done is an acceptable justification. With the digital age upon us, the expectation that services are A

Keep the User Store Clean Over time, dormant user profiles and historical device profiles can accumulate in the user store (directory service), resulting in a significant portion of unused data. This paper presents a simple solution to keep the user store clean by maintaining only active user profiles and device profiles. This solution includes a directory service clean-up process and alterations to the Access Management (AM) Authentication Tree to manage dormant user journey