i6 Encounters Turbulence as it Expands
i6 struggled with its internal authentication technologies as it expanded, which could have led to lost business. Mattos highlights an example: British Airways. “British Airways has 4,000 pilots. And we don't want to be managing 4,000 pilots in our own database.” European data regulations, like GDPR, threatened to make this even more difficult.
i6’s customers have different regulatory needs, different integration needs, and different internal security needs. And when each client requires something unique, configuration can take months. That extra time leads to impatient customers and, often, less secure solutions. i6 needed a partner that could scale with them.
Before Auth0, Mattos faced the prospect of having to “build, effectively, Auth0” by integrating identity providers like Active Directory Federation Services (ADFS) and Okta. “We'd build the first [configuration] for ADFS, and that would work well. And then the next one would come along and it would be Okta, and it would then be, 'Oh, we better build that one then.' And then it would be build the next one, build the next one."
Each client is different, and each would have required its own configuration. Even if i6 built the underlying authentication service, Mattos said, configuration “would take many weeks.”
“It wasn't going to scale effectively and it didn't meet our customer needs,” says Mattos.