We performed a comparison between Omada Identity and WSO2 Identity Server based on real PeerSpot user reviews.
Find out in this report how the two Customer Identity and Access Management (CIAM) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The key benefit of Omada Identity is maintaining complete control."
"Omada offers a technical solution that addresses both our needs."
"Two valuable features of Omada Identity are the ability to discover accounts and link them to identities, and the automatic disabling of inactive accounts or identities."
"Its best feature is definitely the process design. It is quite easy and straightforward to design a process."
"The support for the validity of the resources is valuable. The tool allows resource assignments within a validity period so that the managers do not have to remember to revoke the access once the work is done."
"The benefits of Omada Identity include a holistic way of viewing access, the ability to give people access, and automation."
"The administrative features and SoD are valuable."
"Omada's most valuable aspect is its usability."
"Comprehensive ecosystem."
"The single sign-on procedure itself, as well as the ability to connect to external user sources such as Microsoft Active Directory and LDAP servers, are the solution's most valuable features."
"Some of the valuable features of the solution are the easy integration with processes, such as Single Sign-On. Overall WSO2 is straightforward and does not need customization."
"I would rate the solution's stability eight or nine out of ten."
"It's very easy to implement everything."
"The product provides easy integration between API manager and IT server components."
"The keystore feature has been most valuable for us."
"When the re-certification process is launched that makes Omada very slow. There are performance issues in the current version."
"Omada could make it a bit more convenient to send emails based on events automatically. Having that functionality is critical for us to maintain transparency."
"Improved traceability would be helpful for administrators. For example, let's say a user's permission is being revoked. We can only see the system that has carried out a particular action but not what triggered it. If an event definition or something has changed in the criteria for the permission being removed or something like that, we don't have immediate access to that information. It takes a little detective work."
"Omada Identity has two main issues that need to be solved or improved the most. One is its setup or installation process because it's complex and cumbersome. I'm talking about the process for on-premises deployment because I've never tried the cloud version of Omada Identity. Setting up the cloud version should be much easier. The second area for improvement in Omada Identity is that it's piggybacking on Microsoft's complex way of having all kinds of add-ons, extensions, or setups, whether small or large, such as the new SQL Server, and it's cumbersome to make sure that everything works. Omada Identity is a complex solution and could still be improved."
"What I would most like to see added to the product is role management, especially enterprise or business role management, and the processes around that."
"When you do a recalculation of an identity, it's hard to understand what was incorrect before you started the recalculation, and which values are actually updated... all you see are all the new fields that are provisioned, instead of seeing only the fields that are changed."
"I would like more training. As someone who is new to this world, I don't feel that the courses Omada provides are good enough. They should also improve the documentation. It is difficult to learn how to use the solution by yourself"
"I would like to search on date fields, which is not possible now."
"Sometimes working with the code is difficult because I search for documentation about the code and how to work with the code, which is where I believe they should improve, by providing some documentation on how to work with the code."
"The solution could improve its development from a user perspective."
"I found the initial setup to be very complex."
"This solution does not have BPM workflows already integrated, we had to integrate the BPM module externally. They do not provide full-featured auditing and certification modules out of the box."
"The high availability architecture has to be improved."
"This solution requires extensive knowledge to be used effectively as certain areas of its use are not user friendly."
"There needs to be a good support model and easy-to-understand documentation."
Omada Identity is ranked 2nd in Customer Identity and Access Management (CIAM) with 45 reviews while WSO2 Identity Server is ranked 6th in Customer Identity and Access Management (CIAM) with 7 reviews. Omada Identity is rated 8.2, while WSO2 Identity Server is rated 8.0. The top reviewer of Omada Identity writes "The solution has sped up employee onboarding while reducing manual work". On the other hand, the top reviewer of WSO2 Identity Server writes "Provides valuable API management features, but its technical documentation needs improvement". Omada Identity is most compared with SailPoint IdentityIQ, Microsoft Entra ID, Saviynt, SAP Identity Management and One Identity Manager, whereas WSO2 Identity Server is most compared with Auth0, Amazon Cognito, SAP Identity Management, CyberArk Privileged Access Manager and F5 BIG-IP Access Policy Manager (APM). See our Omada Identity vs. WSO2 Identity Server report.
See our list of best Customer Identity and Access Management (CIAM) vendors.
We monitor all Customer Identity and Access Management (CIAM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
