Okta Customer Identity Reviews

I have implemented a number of applications as far as accessing them through their IDPs. And they're an identity provider; they also provide some alternative active directory slash l dash services. And I have purchased those for getting user data onto other systems.

It's very straightforward. The automation that they have and the way that they let you assign applications to groups or to users and do things dynamically, it is very straightforward other than just that there's a lot of nuance because of the breadth of applications out there that they can work with. It's more a matter of knowing how to work with the security mechanisms in place, such as SAML or OAuth, these may require specific expertise.

As far as our security team is concerned, the ease of implementing multifactor authentication is definitely the biggest value for our organization. Additionally, the single sign-on services provided by Okta allow users to log in to their Okta account and access a variety of other applications. That's why we implemented Connect to leverage this feature more efficiently across MacOS.

The basic idea behind the Customer Identity product is to put in multifactor authentication for clients to make sure that people are properly managed.

It is normally used by people involved with marketing technology.

What it's done for our clients is it's reduced the number of staff they need in order to manage their campus and their partner community services. For example, users can automatically reset their own passwords if they need to, and they've got multifactor authentication so they can easily access the service and they're properly identified.

Using this product helps with the relationship between users and their account managers as well, because account managers can be sure that people are getting access to the services they need.

In Okta Customer Identity, I primarily respond to application handling with around three thousand applications. This includes handling internal applications for permanent employees and third-party applications for contractors. I also work on certification renewal annually and the setup of SSO pages to enhance security.

The most valuable aspect of Okta Customer Identity is the server's reliability, especially for directory and node management. I set up different directories for traffic redirection, ensuring backup when a data center faces issues and maintaining seamless operations.

We use the product for a variety of applications to establish the basic functionality of single sign-on for the company. We are looking for more use cases for our users. We are a marketing company. We have a high turnover rate. The processes are key to us. We are exploring how we can take advantage of Okta to help us streamline processes.

We used to have around 12 systems that had unique logins. There were too many central repositories. Now, we can log in using a single presenter.

We use this solution as a platform for identity and multifactor authentication of the entire platform which is integrated with the active directory so cell phones can be used for multifactor authentication. We have multiple domains and two segregated businesses. We onboard third party applications to Okta and users that need specific applications. The two groups have access to the 11 applications that they need.

The key feature of the solution is the multifactor authentication itself. The app provides a seamless way for users from anywhere to be able to connect. It also offers risk intelligence in terms of track analytics which can determine suspicious log-ons and lock them, preventing breaches. 

I use the solution mostly to integrate into Active Directory to get MFA and other IAM features. In Okta, we can get features similar to those in Active Directory. We also use the tool for authorization and other zero-trust authentication.

We can integrate two-factor authentication with the applications. Two-factor authentication is used for mobile applications like OneDrive.

It's mostly used for customer-facing applications (Customer Identity Management). API management and self-service flows are the most utilized capabilities. It offers a lot of customization in terms of branding, email notifications, and creating a good end-user experience.

For remote access, we have solutions proposed, like Okta Identity Engine (OIE). It has more capabilities than the classic engines. The certificate-based system is one thing, and third-party tools like Intune and Jamf for iOS devices. There is a trust relationship between these device management tools, and that contributes to control over the end-user devices.

We use Okta Customer Identity mostly for SSO (Single Sign-On), and we also use it for user and application management, in particular, for SaaS applications.

Okta Customer Identity improved the company when we used it for user identity management because we were able to manage our user provisioning and de-provisioning through the solution very efficiently.

If users are joining the organization or if they're in the onboarding phase, we can take care of the applications and all other requirements through Okta Customer Identity.

When users are leaving the organization or when they're in the off-boarding phase, we use the de-provisioning feature in Okta Customer Identity for those users.

We're very happy with the solution and its features.