Share your experience using Atlassian Crowd

My main use cases with the Okta Workforce Identity include preparing my certification and doing integrations such as org-to-org integration or Active Directory, and it is mostly about integration.

As an individual user, I appreciate that I can create my own lab with Okta Workforce Identity. They provide instances for me to create almost ten instances to test.

Some of the best features with Okta Workforce Identity are configuring the SSO through Okta to Okta. For me, it was the certification and the integration I worked on because it was my pathway to prepare my certifications, along with the directory and network security, the IP zone and related components.

We use the Single Sign-On feature with the Okta Workforce Identity, and I configure it through the platform, especially for Okta-to-Okta. From one instance, I could switch to another using the SSO, as Okta to Okta allows the SSO feature.

The impact of SSO on my IT overhead and user experience has been significant because it reduced authentication fatigue, password sharing, and password reusing. For administration, it is integrated, and it is great for IT support. For the end user, it is beneficial as they do not have to remember a password or keep the password on a post-it for different applications; they just authenticate once to access several services and service providers.

Areas for improvement with Okta Workforce Identity would be in the governance place; for me, it is light. Okta is mostly focused on execution and runtime, which means maintaining authentication and ensuring people connect with the appropriate session. However, it could improve in the governance part, particularly regarding better role management and workflow, as I feel it is tedious on Okta. I think Okta could enhance the governance area of identity.

I have not personally experimented with technical support from Okta Workforce Identity, but I see there is a good community and many resources available. I have not tested Saviynt's support either, but I know there is direct contact with Saviynt support.

I cannot rate the support for Okta Workforce Identity directly because I have not experimented with it; however, I notice good communication within the community, but it would not be fair to rate them without personal experience.

Positive

I have tested different solutions before Okta Workforce Identity, including Saviynt and SailPoint, and decided to go deeper into Okta because it allows me to create my own lab. I worked on a homemade solution for about three to four years back, spending five years on that project.

My experience with the initial setup of Okta Workforce Identity is that it is straightforward and not huge. The initial setup is simple and, considering it is a SaaS solution, it is easier. I have tested the connector, which is available for on-site solutions for Active Directory, and there is still a lot of infrastructure relying on Active Directory.

Regarding experience with pricing for Okta Workforce Identity, I do not have the pricing on IGA solutions or IAM solutions, but from my study two years back for a project, I found it is not that huge.

The main differences I notice between SailPoint and Okta Workforce Identity for the IAM solution suggest that they are in different categories. SailPoint is mostly for the admin part, while Okta is excellent on the runtime section, focusing on secure authentication and SSO. SailPoint is used for configuring identity with the right entitlement while Okta is about ensuring secure connections and efficient user authentication.

I would rate Okta Workforce Identity seven out of ten.

The use cases for Microsoft Active Directory are managing all users on-premises. We have over 200 employees and multiple computers, approximately over 200 computers. We have shared computers and shared user accounts, which is why we use Microsoft Active Directory, along with Group Policy and all that other functionality that comes with it.

The best features of Microsoft Active Directory are the OUs, the groups, and how everything is set up relatively quickly. If I change a password or need to reset a password, the information propagates relatively quickly, and the structuring inside is easy to understand and use. It also works effectively with other Microsoft products.

I would assess the impact of Microsoft Active Directory's centralized domain management on our organization's security protocols and access permissions as satisfactory. Our protocols are relatively good, but with different vendors, many that need service accounts utilize legacy systems which aren't up to par, requiring us to make exceptions.

There are a few areas that could be improved with Microsoft Active Directory, along similar lines as Intune. Not too much on the support side, but on the Group Policy side, it doesn't always function as intended. Sometimes, it can be overly complicated, and when you apply Group Policy in an Active Directory environment, sometimes those settings apply and sometimes they don't.

I've been using Microsoft Active Directory for over 3 years, and we've had no problems. It runs continuously, so it's always operational.

The deployment experience was rated as seven out of ten.

I've been working with Microsoft Active Directory for over 3 years, and we've had no problems. It runs continuously, so it's always operational.

Microsoft Active Directory scales effectively; I don't foresee any issues with that at all.

The initial setup of Microsoft Active Directory is complicated, especially with an existing Active Directory. You have to demote the existing AD, promote the new AD, and set up synchronization between the two, as you should always have two Active Directories so they replicate between one another.

The pricing, setup cost, and licensing with Microsoft Active Directory is straightforward; you just buy the server and then have to buy the user CALs.

I have used Microsoft Active Directory for a long time, but not with Intune, just as a stand-alone solution. I now use Microsoft Active Directory along with Intune.

Microsoft Active Directory Federation Services for secure single sign-on has worked effectively. We don't utilize it with other businesses, but with the whole hybrid and Intune AD and the sync between everything, it functions relatively smoothly.

The integration of Microsoft Active Directory with third-party applications has helped with interoperability in our IT environment. Examples include different applications we've utilized before, such as NetGate, where we use the LDAP feature built into Microsoft Active Directory for single sign-on. We've used it for other open-source software and proprietary software integrating ADFS, which has been helpful for authenticating against the domain to other third-party applications.

On a scale of 1-10, I rate Microsoft Active Directory a seven.