Try our new research platform with insights from 80,000+ expert users

IBM Cloud Identity Service vs Okta Workforce Identity comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 2, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Cloud Identity Service
Ranking in Identity and Access Management as a Service (IDaaS) (IAMaaS)
31st
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
3
Ranking in other categories
No ranking in other categories
Okta Workforce Identity
Ranking in Identity and Access Management as a Service (IDaaS) (IAMaaS)
3rd
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
67
Ranking in other categories
Single Sign-On (SSO) (2nd), Authentication Systems (6th), Privileged Access Management (PAM) (7th), Access Management (4th), ZTNA as a Service (11th)
 

Mindshare comparison

As of July 2025, in the Identity and Access Management as a Service (IDaaS) (IAMaaS) category, the mindshare of IBM Cloud Identity Service is 0.5%, up from 0.4% compared to the previous year. The mindshare of Okta Workforce Identity is 12.1%, down from 14.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Identity and Access Management as a Service (IDaaS) (IAMaaS)
 

Featured Reviews

reviewer1054431 - PeerSpot reviewer
Excellent support, beneficial integration, and low maintenance
I have found IBM Cloud Identity Service to be highly scalable. It can handle thousands of users. IBM solutions are truly enterprise-grade. You don't find a lot of use cases for small businesses, or even sometimes medium businesses, the price point does not fit smaller businesses. The implementation effort, it's hard to find that cost-benefit.
Tor Nordhagen - PeerSpot reviewer
Extremely easy to work with, simple to set up, and reasonably priced
The drawback of this solution is that in our shops, many staff members sometimes have to be borrowed from one shop to another and the solution does not really support having multiple roles. The user experience we would like to have when a person works in shop A which pays their salary is that they should have access to pretty much everything. Maybe you have somebody who is a manager in that shop A, he should be able to order new wear, he should be able to change the pricing, he should be able to empty the cash registry, and ship it to the bank. But when for instance, in COVID, people had to fill in for people in shops where a lot of people were sick, then they had to actually use user accounts of people that work in shop B. If you were employed in shop A, you could not work in shop B without borrowing somebody else's user ID and password. Which is really bad. We haven't been able to work around that and Okta Workforce Identity does not have a solution for it. We are now piloting their identity governance solution. Obviously, it's easy to give somebody access, give them an account, and give them roles, but it's hard to maintain that. For example, if you moved from, say working in a shop to working in a warehouse. But why do you still have all this shop access? The solution has until now not had anything to really support the process of taking away access. But now we are in a better release program of Okta's identity governance solution. Although it's very basic, the solution has started on a journey, but identity governance is something that Okta Workforce Identity really needs to improve. The ability or the options in the solution for changing the look and feel are not good enough because in our partner portal, essentially what they have is an ugly admin interface. The admin interface is good enough for us technical people because that's all we need. We work with the product and we're able to see the data but when it comes to presenting the service portal, Okta Workforce Identity does not have any capabilities really for making it look pretty. To add branding and different graphical user interface elements than Okta basic for essentially delegated admin for the business-to-business portal is horrifying because you're essentially using the tech admin. The only option we had and used, was to take the tech admin console and strip it. so that a vendor that has some goods that are sold in the shops, when they want to add a user on their side, say a driver or a packer on their side who should know how much they've packed in a truck to come to our warehouse, then the user interface that this vendor is using, these functional people will then have to use an extremely basic user interface.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"One of the most valuable features of IBM Cloud Identity Service is that it delivers integrations with the commercial SaaS software that's available."
"It is stable. We can automate many of our daily operations with it, and we don't have to manage many things manually."
"It is multiple identity and access management, so all of the applications are valuable. It's also part of the automated process."
"Other than Okta being an easy and awesome integration tool, one of the best features it has is the provisioning and deprovisioning, which makes management way easier. You don't need to be too technical to understand how it works."
"Stability-wise, I rate the solution a ten out of ten."
"I am able to authenticate my users on cloud and SaaS applications such as Workday through Okta workflows."
"The solution so far has been very stable."
"My total rating for Okta is ten out of ten."
"A solution that's easy to use, stable, and reliable."
"The initial setup is easy."
"The most valuable aspects of the solution are the integration with external websites one-factor authentication."
 

Cons

"Everything can be more stable and secure. There could also be more account features. I would like to be able to do more things through it to manage users' accounts."
"IBM Cloud Identity Service is going in the right direction with the product. They need to keep building out the integrations and having the library is very critical."
"The initial setup is complex, it's not straightforward. It takes months because it's not straightforward."
"The solution’s policies are difficult to understand due to the policy methods. They use authentication. The solution’s workflow is also difficult and not very active. They need to have proper documentation on it. In the next release, I would like to see the workflows being more digestible."
"You can't hide the device when you're checking logs."
"The only area of concern in the solution stems from the fact that my company needs some help regarding the setup phase from a partner."
"The solution should have greater on-premises availability, not just cloud and more package customization in its processing."
"UD attribute mapping, Okta group rules, and dynamic usage could use improvement. It also needs more in-depth functionality and features to integrate with RADIUS solutions."
"We have experienced some challenges in integrating this solution with Scope and Cognito."
"The initial setup can be complex at first."
"It would be pricing, which is a tough one because it goes against Microsoft. A lot of companies say they're a Microsoft partner, and they get all their software for free. Okta is like a luxury product, and it's not the most affordable one. I would say if they could work on pricing, it would help. Other than that, they've done great strides in developing a product that is really good. The companies that do see the value tend to invest in it."
 

Pricing and Cost Advice

"The price of the solution is expensive for non-enterprise companies. IBM's always going to be a little more expensive, you're going to be paying a premium. However, depending on the organization's needs, there's probably a benefit there to do even with the price being the way it is."
"The solution's pricing model could be better for SMBs."
"The product's price is high. For each feature, a certain payment is required."
"Workforce Identity is well-priced."
"The product is expensive compared to other vendors."
"The product has a user-based license model."
"License is around US$20,000 annually."
"The licensing is per user per month and includes full technical support."
"The price of the solution is good."
report
Use our free recommendation engine to learn which Identity and Access Management as a Service (IDaaS) (IAMaaS) solutions are best for your needs.
860,168 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Computer Software Company
15%
Financial Services Firm
11%
Manufacturing Company
9%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about Okta Workforce Identity?
Okta has introduced the Universal Directory. It has custom attribute capability and user permissions to read/write on their profiles or hide them. Profile sources and identity profile sourcing are ...
What is your experience regarding pricing and costs for Okta Workforce Identity?
Pricing for Okta is reasonably not that much, however, I don't have access to the commercial aspect.
What needs improvement with Okta Workforce Identity?
I believe that if we integrate the workflows section into the main Okta Workforce Identity dashboard, it can be very useful.
 

Overview

 

Sample Customers

Baxter Healthcare, 
FedEx, Zoom, Takeda, Lululemon Athletica, GrunHub, jetBlue, McKensson, Bain & Company, Engie, Peloton, Sonos, T-Mobile, Hewlett Packard, MGM Resorts, Ally Financial, Priceline, Albertsons, Itercom, Classy, FICO, Kensho, Live Nation, Drata, Rotary, and others.
Find out what your peers are saying about IBM Cloud Identity Service vs. Okta Workforce Identity and other solutions. Updated: June 2025.
860,168 professionals have used our research since 2012.