Bitium vs. Microsoft Entra External ID

Best suited for companies that use the same services across multiple teams, services that might require support at one point. For us, it is very easy to share access to either the IT support team or to me, as the Salesforce administrator, and we can easily take care of the issue and then log out without any hassle.

I would not strongly recommend it for single users, who don't need to share access to others.

Incentivized

It is not easy to calculate the actual ROI due to the difficult quantification of all factors, but it certainly contributed a lot in protecting, monitoring and controlling access to our system. It also made it much easier to detect vulnerable external users with simple and "easy to hack" passwords they use on multiple apps.

• Sharing access. It's as easy as 1-2-3 with Bitium, no more hassle with sharing the actual password and then changing it, violating company policies, etc.
• Lots of apps supported. In all three years since we are using Bitium, we haven't encountered any app that would not be supported by it.
• Easy to set up strong passwords. Another very easy and intuitive feature: when you are setting up an app, you can ask Bitium to generate an A-level password automatically, that you can therefore use with ease.

Incentivized

• Single sign-on simplifies access to your apps from anywhere
• Strong authentication for your customers using their preferred identity provider.
• Integrating with social accounts such as Facebook or Google+

Incentivized

• Apps crashing. From time to time, some apps stop working in Bitium and they come back only after a while (1, 2, 8 hrs). We don't have a clear explanation for this yet.
• Very tied to Chrome. Bitium is almost 'married' to Chrome, making it unusable in other browsers, which is sometimes problematic.
• Sometimes slow Chrome Add-on. From time to time, the add-on seems so unresponsive that it is easier to go to the web dashboard and log in from there in the app you were looking for.

Incentivized

• Troubleshooting diagnostic logs effectively requires VS Code
• Group and role management requires additional effort
• The programming model (XML) could use some developer experience love

Incentivized

Each one of these alternatives has pros and cons. PingOne from Ping Identity states they "help deliver the secure and seamless customer experience to win battles for customer acquisition, retention, revenue, loyalty, and trust." While that may be the case, they did not fit our needs. We have a complex system and it did not seem to fit into our business.

Incentivized

• Everyone is now required to have A-level passwords, so the overall level of security has increased a lot.
• Having a secured way of sharing access to different apps, users are now very open to being helped more hands-on by the support teams, not fearing that their credentials might be exposed or later used.

Incentivized

• Having monthly active users billing was cost-effective.
• Helped with the IT support that was already managing the Azure platform of the company; this helped to manage the costs better and optimize them.

Incentivized