Okta Workforce Identity Reviews

This solution has a lot of capabilities and features. 

The cost per user for this solution is really high and could be reduced. 

We have experienced some challenges in integrating this solution with Scope and Cognito. 

This is a stable solution. 

This is a scalable solution. 

We have been satisfied with their customer support.

Neutral

I would rate this solution a nine out of ten. 

We use this solution for MFA and single sign-on.

It's our enterprise-wide identity management system. It identifies all of our users prior to accessing any of our applications.

It assures us that everybody is authenticated prior to accessing any corporate applications.

The most valuable features are multifactor authentication and single sign-on.

It's reliable and it does what it is advertised to do.

The guest user access could be improved. How do we authenticate people that aren't in our Active Directory?

In the next release, I would like to see passwordless access.

I have been using this solution for four years.

We are working with the current version.

This product is very stable and is one of our best applications. It's the most reliable application and it never goes down.

It's a scalable solution and we are able to add users as needed.

We have about 4,000 users and it's all employees and contractors within the company.

Every employee uses this solution every day, multiple times a day, and we plan to increase usage.

They meet our needs. 

We haven't had a problem with technical support answering any of our questions.

We went from using nothing to Okta Workforce Identity.

The initial setup was straightforward.

It was a week-long process to deploy.

We need one and a half persons to do the configuration, maintain this solution for administrators and the development.

We completed the implementation in-house.

We have seen a return on investment by using Okta Workforce Identity.

I can't discuss pricing.

Follow along with what Okta recommends.

I would rate Okta Workforce Identity a ten out of ten.

Intergated on-prem and cloud applications on multi-tier domains and user identity accessing applications hosted on cross domains. Full fleged automation using AD and Okta groups for app assignment. 

Lifecycle Management of apps on our Okta tenant. 

• Central administration of Apps
• Auto activation of user accounts/ Just-In Time Provisioning
• Global App availability
• Less or No Administration required

1. Active Directory Sync, as its useful for pre-assigning apps, can also be used for de-provisioning apps for exiting users

2. Shared apps with common password can now be managed centrally without revealing the credentials

3. User and Apps Management

4. Desktop Single Sign On

5. Auto-provisioning

6. Flexibility to integrate In-house applications

7. Password Self Service

8. Support non-domain users

9. Group based app assignment (okta, AD, pushgroup)

10. Adaptive MFA

11. Workflow for app requests

Command line access

Reporting

Since 2015

It's very stable we have 99.999% uptime on the base

Very high and secure, we have more than 170+ apps secured for sso

Customer Service:

9 out of 10

Technical Support:

9 out of 10

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

Initial setup is straightforward, simple and easy to manage

Some apps needed assistance from Okta support team.

Setup is simple if you are an AD admin, cost comparison is nominal compared secured access

KB article from Okta is very detailed just spend some time on the okta

• Supporting SaaS implementations from corporate login.  
• I'm a consultant and have worked with Okta at two clients. Both had started to leverage Okta for single sign-on to SaaS services and internal systems. One was more advanced, the other was only doing limited federation and not taking advantage of the power of Okta.

Okta improved both organizations where I've worked with it: 

• Better Single Sign-On (reducing the number of passwords)
• Improved accountability (to know what users were doing, and where they were working on Identity and authentication services)
• Authentication (where Okta's own MFA solutions or work in combination with Duo were very useful for strengthening the security of major systems)

Okta's great for their federation capabilities where it lets the IT team enable business with anyone using common federation features across SaaS, PaaS, IaaS, and internal applications. The Multi-Factor Authentication capability lets you address one of the biggest challenges around security - MFA to make it hard for adversaries to get into your systems.

Better multi-factor authentication integration and support, it's around v2.0 and will need a 3.0 release for maturity.

I am not using the custom identity aspect; I use it only for customers and staff. We wish to sell the customer EIM because, at the moment, they have a SaaS solution. You can use Microsoft Azure to host Workforce Identity.

Okta is a very compliant solution, and it is easy to deploy.

It is not very interesting from a marketing perspective. For this, you can use open source solutions to reflect different groups.

Customer EIM is a new concept, and historically we use the customer EIM for the questionnaires or with focus. We have been using it for about 7 years.

It is a stable product.

It is a perfect solution in terms of scalability.

Technical support is excellent.

All the providers of EIM have the same licensing model. If you have 10 million users or customers of Okta, it is just one payment. However, it is costly in this case. The licensing model is unique to each user. Each user costs 10 euros. Therefore, if you have 10 million users, that's almost 100 million, so it is costly. The model is effective, however. Each user's identity is unique. It is cheaper for small companies and organizations, as they have fewer users. It is dependent on the evolution of your user base. It depends on usage per user, so the more sign-ins there are, the more expensive it becomes, so it works best for smaller companies from a financial perspective.

We considered Arribatec, which is a new startup solution in the market.

If you require identity solutions as a service, I would recommend it, but it is dependent on the use case. I would rate this solution 7 out of 10.

• SSO
• Lifecycle management (provisioning / deprovisioning)
• Mobility management

We've integrated our HRIS system with our Active Directory/Office 365 using Okta. We're able to shift away from Active Directory as a master and allows us to be more mobile with our remote employees. Account creation and disabling people on time has made our team more productive.

• A couple of improvements with the lifecycle management that will help companies that don't have an HRIS system to help manage contractors and contingent workers would be to add ways to disable their accounts once a certain time point is designated.
• Also, an improvement to the reporting capabilities can make running reports easier and more customizable.

I have used it for four years.

We have not encountered any deployment issues. The support team has been amazing.

There was just one small downtime with the DNS attack that affected many cloud companies.

We have not encountered any scalability issues.

Customer service is excellent.

Techncial support is excellent.

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

We implemented it in house with the consulting team.

The Okta application network is a huge component of the company that will grow with the industry. If customers are asking for things, then Okta will consider adding it.

I have used Okta for security purposes. It grants access only when you have the proper credentials, which I find essential for utilizing new technologies and web applications.

The most valuable feature of Okta is its security. You can only log in if you have the access, which protects the applications by avoiding cross-site scripting. Hackers cannot access the system directly. Only after receiving a message from Okta, you can log in, making it highly secure.

We are facing one issue with Cypress test cases. Whenever I write Cypress test cases, we encounter problems with logging in through Okta. There is no proper documentation on integrating test cases with Okta, and this issue is troubling whenever I try to implement it.

Okta is a stable product.

Currently, scalability is a top priority, but there are no issues with adding many users to Okta.

Before Okta, I manually created portals using a username and password stored in a database. Okta introduced a different process.

Initially, it was complicated to set up since I was a beginner and there was no proper documentation. Now that I am more experienced, it is easier to handle.

I need to analyze fully in the future, and if I do not have any concerns, I will share any with you via LinkedIn. As of now, I do not have any additional advice.

I'd rate the solution eight out of ten.

I find the provisioning features and the integration with other applications useful.

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.

I have been using the solution for six months.

The solution is stable.

The solution is scalable. We are a medium-sized company and we use it full scale. There are around 200 users for the solution. It also requires two admins.

The solution’s customer support is fast, reliable, and helpful.

We didn’t do the deployment because it was difficult. We had to rely on an in-house team.

Our in-house team deployed the solution.

The solution’s pricing needs to be reasonable. You are dealing with a lot of components and the pricing is component-based.

I would rate the solution an eight out of ten. I am pretty much satisfied with the solution since it works properly. Anyone looking to implement the solution needs to read the documentation carefully. They also need to have a bit of experience before that.