Previous to using Okta Workforce Identity we used Oracle Access Manager and it was horrible. Oracle Access Manager didn't scale, it had a lot of bugs, and it was expensive. Oracle was charging obscene license fees for a product that was rubbish.

I've also used JumpCloud and have started to compare these two solutions. 

Compared with Okta Workforce Identity, Microsoft Entra ID is challenging to use in terms of integration and troubleshooting.

I have worked with Microsoft Azure, Slack, Teams, and Adobe Creative Suite. Microsoft Azure and Okta Workforce Identity allow applications to be implemented similarly. The process involves having an extension for the application, often a download file. However, it's important to note that while this implementation works on PCs, it might work on Macs.

We used ForgeRock, and we switched to Okta mainly because of the flexibility that Okta provides.

ForgeRock requires on-premises maintenance. Because most of our applications are now on the cloud, Okta is more user-friendly in that sense.

A couple of years ago, it was 70/30, 70 being on-premises. That's why ForgeRock was the choice. However, it's flipped now to 30/70, and Okta is more useful.

We still use ForgeRock because you can do an on-premises hosting for ForgeRock. Okta doesn't have that capability.

I have previously used Oracle Access Management, Microsoft Azure Active Directory, and ADFS. Those would be the major ones. I've been introduced to small ones, such as PingFederate, but I never used those heavily.

We switched solutions because of the architectural design. We chose Okta Workforce Identity for external customers, it's a customer identity platform that we decided to go with.

The company used RSA before I joined. I believe they switched because they preferred a SaaS platform, and RSA was late to adopt this model. RSA is excellent as an on-prem solution, but they didn't transition to the cloud until later. 

We previously used a different solution. We moved to Okta as the GUI is very user-friendly, and the solution is simple to use. 

I did not have another access management solution in place prior to implementing.

We went from using nothing to Okta Workforce Identity.

Prior to working with Okta, our clients had native solutions.

We have not used other solutions.

Prior to Okta, we were working with Active Directory.

We are using Azure for authentication and I really like Okta compared to that. Okta is more extensive than the product from Microsoft Azure.

I have had experience with Ping and ADFS but not at the places I have worked; only with customers.

Yes, we had previously used a different solution which was replaced by Okta. Non-scalability was the major drawback of our previous solution.

We did not previously use a different solution. Okta was the industry leader.

I'm not sure if any other solution was used previously. When I joined the company in 2020, I start using Okta, and I don't know if they had any previous applications.

We previously used Workspace One Access Solutions from VMware. In fact, we're using it as well as Okta, so we never really switched.

I previously worked with One Identity Manager and IBM Identity Manager.