Upgrading Identity and Access Management Across Multiple Apps

Identity and Access Management, or IAM for short, can be quite a complex topic — while the interface should strike the optimal balance between simplicity and security, making sure ‘the parts work’ is quite an intricate affair.

(Don't) DIY – Or Else Die

Often, teams start out with building their own login as part of an MVP or V1.

There's nothing inherently wrong with that.

However – as you move forward, replacing your home-cooked login and authentication solution with a robust IAM tool becomes more and more sensible:

• Maintaining an own IAM solution as part of your application means that you’re responsible for maintaining and update it — which is time-consuming and thus also costly.
• More importantly, it requires diligent updating according to new threats and standards — or risking compromise.
• Also, it’s cumbersome to scale and upgrade — e.g. when you want to introduce Single Sign-On or a new method of authentication like Social Logins (such as OpenID Connect or SAML 2.0, like OAuth via Google).

IAM confused?

If you'd like to know more about this topic, I wrote a case study about it – find it here, via a paywall-free friend link:

https://medium.com/@bertrand.rothen/upgrading-identity-and-access-management-across-multiple-apps-product-management-case-study-28b2eb8bbfc5?source=friends_link&sk=c72600690390303c4b5923c908be7850

Thanks for your attention! ??