The initial setup is very easy. Building a new environment is easy because nobody is better than Okta Workforce Identity when it comes to deployment. I give the setup a ten out of ten for ease.

The initial setup is complex. However, you have all of the documentation and if you follow the directions, you can manage the setup well. It will be done correctly. Also, if you need help, their support is also available, and they are quite helpful. 

We had two people handling the deployment. 

Setting up Okta Workforce Identity has to be done gradually because you have to change the log-in methods for every application, meaning you need to turn them on. For example, now you'll start to use Okta Workforce Identity for Office 365. Next, you'll use it for Zendesk. You cannot do everything at the same time, so you have to make a gradual plan over a couple of months, then you turn on all of the new applications for authentications to be done with Okta Workforce Identity.

Deploying the solution took two months.

The initial setup is easy. Once you understand the steps, it's straightforward. There are three steps: enrolling users, removing tenants, and updating field metadata from outside the application and SaaS integration. Deployment depends on the number of occasions, testing, and the users. If you have 30,000 users, you will need two months. I rate the initial setup a ten out of ten.

The initial setup is simple. I rate the process an eight out of ten. It takes a few weeks to complete the integration for different projects. It is a reasonable time.

The deployment team includes administrators for the applications, as they are responsible for configuring integrations from their side. The administrator plays a crucial role in integrating the Active Directory. The project may require a collaborative effort of approximately three to five individuals. It requires two engineers for maintenance.

The tool's deployment is straightforward. You begin implementing applications once you've established your IDP. Deployment doesn't need a team of people. It can be done with the help of one person. Setting it up and integrating applications typically takes about a week, with additional time required for a more extensive list of applications, ranging from 50-100.

The product is not difficult to maintain once you have integrated it. 

The initial setup is very straightforward; it's a very simple setup. There are some areas for which you need some skills. If you have an SOP, you can just follow it. I would give it a four out of five.

We have three people assigned to the solution for deployment and maintenance.

The initial setup of Okta Workforce Identity is straightforward. I was able to get an environment ready within half a day.

I rate the initial setup experience of Okta Workforce Identity a four out of five. 

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight out of ten.

The product's initial setup phase is straightforward.

The solution is deployed on the cloud since it is used at a company-wide level in South Africa.

The initial setup is very easy. It's not complex. 

The deployment took a matter of three to four days for our hybrid setup.

I rate Okta eight out of 10 for ease of setup. It's a SaaS product. You can configure it in a few hours. It takes additional time if you use on-prem agents. Active Directory has some other agents that must be integrated. It will take additional time. Otherwise, it won't take much time. You need three people at most to deploy it. Usually, one person deploys the solution, and two other people are on standby. 

It was straightforward for access management with SSO and MFA. It was complex to implement password synchronization between AD domains.

The initial setup wasn't so easy but it wasn't too complex either. We had assistance from Okta for the installation. Implementation didn't take long, maybe two or three days but we had some issues with some applications, and we had to postpone our deployment for about two months because of that. There's no maintenance required. We have about 300 users dealing with the solution in the company and it's used daily. We have no plans to increase usage for now.

The initial setup is straightforward. We deploy it on the cloud. The product has good documentation to refer to for implementation. We require two engineers and one manager to execute the process.

The initial setup is pretty easy. It is very simple to set up initially and it takes a couple of hours. The multi-factor authentication is simple too and can be turned on as required. The one that takes the most effort is SAML, which is the integration with the service providers. That's full-service integration and that's because a lot of service providers do it all their own way. You have to work with each of them as they come up.

In terms of how many people you need to maintain the product, it depends on how you do it. We're managing it for a couple of customers, and it's just me. However, what I've done is, I've put an API, used the API, and put a front end on that to make it easy to do the onboarding and offboarding. I don't deal with the day-to-day issues, that's done by the HR department.

The initial setup was straightforward. The deployment took approximately two months.

I would rate the initial implementation of Okta Workforce Identity a four out of five.

The setup was straightforward. Nowadays, all the other IDPs are the same way, too. I didn't find a single IDP that had no experience at the level, and all of them can stand up at the same time, within the same time frame.

With Okta, on the other hand, the requirement to have the ID server in between, whether it's the cloud-based ID server specified, or the on-prem base, like ours: It's on-prem, but what I found was that we were not able to do it even after following all the guidance unless we had a dedicated Okta person to help us do it. It was a different situation with Microsoft and cloud IDP which were easy to set up, as we were able to do it ourselves just by following the documentation.

I haven't personally handled the deployment, but I've worked on configuring the printer, which wasn't too complex. As for deployment time and manpower, it's a bit different since Okta Workforce Identity is a cloud-based platform. We don't need dedicated servers as Okta manages integration. We work on our own tenants, and Okta provides preview environments for testing new features. As for maintenance, it's not too difficult, especially for premium customers who can raise support tickets if needed.

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.

The initial setup is straightforward.

We currently have one customer deployed on AWS and another on Azure.

The initial setup is pretty straightforward. I rate the ease of setup eight to nine out of ten. The deployment took two to three weeks. One person is enough to operate and maintain the solution.

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

The initial setup of Okta Workforce Identity was straightforward. The deployment took us approximately one and a half months. This included many different applications and services.

The initial setup was straightforward.

The initial setup is really easy.

We do a lot with Okta but the setup was still very easy.

The initial setup, for new users, is a bit difficult. It does get easier with time and practice, however. It's complex in that when you jump into the dashboard and you look at the screen, it's either a mish-mash of information, or, it starts off with a single sign-on, and then you have to look at the other components. They force you to look for the other components within menus. Everything is hidden. It's not clearly defined when you open the dashboard. That's one of the hurdles that we've had when setting everything up. It's just not intuitive and not clear where all the elements are in the menus.

As a SaaS solution, the product does not require very much maintenance at all. Any maintenance is more around governance and administration.

Initial setup is straightforward, simple and easy to manage

The initial setup is intermediate. A security solution is not supposed to be easy to apply. It's supposed to be somewhat bureaucratic. That said, the setup itself leans towards being straightforward. We didn't have any issues with the setup.

I'd rate the ease of implementation at a seven or eight out of ten. 

I'm not sure about maintenance requirements, however, our company has a limited IT team of about three or four people, and therefore it's likely not too maintenance-heavy.

Okta Workforce Identity was easy to install, it is user-friendly when it comes to implementation.

Its initial setup is straight forward. Okta tenant creation can be done quickly. Adding users and applications to the okta platform has customer dependabilities. Integration and going live with O365 also takes a little bit more time than other apps because of internal rollout and user training. It is not an Okta problem but needs customer Microsoft teams active involvement 

The initial setup is almost completely straightforward. The identity action is complex, so it makes it just a bit difficult.

The initial setup is easy.

It's pretty straightforward. If you need it, you get great support from Okta as well.

They provide a lot of datasheet information and step-by-step ways to deploy the solution. They're doing really well on this front.

The platform can be deployed on the cloud.

It's on a cloud platform, so all you have to do are the configurations.

The implementation was rather straightforward. It wasn't too complex or difficult. We had some issues, however, they were solved.

Deployment took about a month or so. 

We had two people handle the deployment. 

The initial implementation is not overly complex. It's easy. It's rather straightforward. A company shouldn't have any issues with the setup process.

The deployment is pretty quick. We had everything set up within a week or so. It's not a long, drawn-out process by any means.

Setting up the MFA for Windows RDS was very straightforward. Using it with Tableau was not very straightforward. It was a bit complex, but the documentation was handy enough to set it up.

It was easy.