Build vs. Buy
Using OAuth 2.0, abas began working through the complex problem of securely managing the interaction of thousands of customers with real-time expectations as part of their research into an identity access management (IAM) solution.
But fully executing on their vision would mean pulling developers from their core mission of product expansion and dedicating a team to regular maintenance and upgrades. Choosing to build in-house would also render hitting their go-to-market deadlines a challenge.
“In today’s world, with cloud computing services and microservices, integrating with other packages which specialize in a specific industry is usually a lot more cost- and time-efficient than just doing it all by yourself,” Dormont says.
They quickly realized that a fully-featured, out-of-the-box solution would be more efficient than pursuing the challenge in-house. “Why reinvent the wheel when you can partner with an IDaaS provider trusted by more than 500 enterprise companies and thousands of others?” Dormont says.
A potential third-party partner would need to offer a multi-tenant authentication that could handle federation and user management. In addition to enterprise connections like Active Directory (AD), their preferred out-of-the-box solution would also offer multifactor authentication (MFA) and web tasks, as well as the extensibility to scale with abas road map.