I have hands-on experience with Okta Platform for a little over three years, starting in 2023, integrating SaaS apps with SAML, OIDC, enabling MFA, including WebAuthn and FIDO2, and building group-based assignments.

Since then, I have day-to-day admin tasks including app onboarding, policy tuning, certificate and metadata rotation, lifecycle automation, HR-driven processes, and troubleshooting SSO issues end-to-end, including IDP and SP log attribute mapping and role entitlements.

The main use case is centralized SSO and MFA for internal apps with event-driven lifecycle automation and JML to enforce least privilege and clean deprovisioning. Some examples from a typical day include onboarding new hires every morning via HR events from Workday, ensuring the right access is provided and provisioning automatically to enforce MFA while keeping auditors happy regarding least privilege and SOD.

The HR trigger, such as Workday pushing a new hire to our IAM workflow, allows Okta Platform to serve as the IDP and source for app access, mapping job codes and departments to Okta Platform groups, such as sales to US finance analyst, while integrating apps toward Snowflake with read-only permissions. After integrating apps, the SSO setup gets done with SAML or OIDC protocols with Okta Platform as the IDP, validating NameID, subject format, sign, and encrypt settings while rotating all SP or IDP certificates as per schedule.

Subsequently, MFA and conditional access are arranged where policies require Okta Verify push on everything we engage with. We also manage attribute governance by maintaining profile mapping, including username, email ID, and department entitlements. App rules are assigned via groups, followed by monitoring and troubleshooting, ensuring a smooth deprovisioning process. For leavers, Workday termination revokes Okta Platform account and app assignments immediately, resulting in new hires being productive on day one while keeping admin efforts low and long ticket trails rare.

Automation has acted as a force multiplier for my workload and my team's efficiency. We moved from ticket-driven manual steps to a predictable policy-driven flow, making onboarding faster, cleaner, and far less noisy.

Okta Platform has positively impacted my organization through measurable risk reduction, faster onboarding, and fewer tickets. The concrete data indicates that the onboarding cycle time reduced by 50 to 60%, from one to two working days down to two to four hours for most SaaS apps. The day-one access rate has increased from 78 to 96%, with a relative score for new hires having required apps by 9:00 AM on their start date. Furthermore, the ticket volumes have fallen by 30 to 40% over the quarter.

View full review »

We had a bunch of Active Directory servers, Windows Active Directory servers on-premises. We did an Okta Platform agent installation on those servers to synchronize the identities from Active Directory to Okta Platform. We then leveraged that integration and configured it as an Identity and Access Management and SSO solution.

I used Okta Platform as Identity and Access Management, which served as the source of truth for every single application entitlement and role-based access. Role-based access was a particularly important feature. Multi-Factor Authentication was essential, and I am using and consuming a lot of those even today for a couple of applications, though I am not managing that particular Okta Platform instance as it is managed by a third party. Identity and Access Management, Multi-Factor Authentication, role-based access, and SSO were all critical components, serving as the source of truth for the entire application footprint. I also used Okta Platform for Zero Trust Network Access on the consumer side, which was a Palo Alto engine that I integrated with Okta Platform.

Okta Platform is a SaaS service, not something which you have to host yourself on-premises. Of course, you need agents to synchronize if you are already moving from a traditional on-premises identity-based architecture. Okta Platform is SaaS-based. While there are competitors such as Ping Identity, which used to be a great one but has since been acquired, and Microsoft Entra, which does all of it as well, Okta Platform has a lot of advantages. Okta Platform has very rich integration capabilities with a lot of other vendors, including deep integration capabilities with Zscaler, CrowdStrike, most of the ZTNA vendors, and CASB vendors. The number of applications that you can natively integrate with it out of the box is quite huge. Another advantage is the risk-based authentication capability, where Okta Platform gives you the capability to have step-up authentication based upon superhuman activity or unusual login detections. MFA is fairly seamless, and while it is not something that Okta Platform is doing alone as others are doing it as well, Okta Platform is stable with no issues with downtime or maintenance. I never had any challenges with that. The rich integrations are a significant advantage.

View full review »

I don't have many details about Okta Workforce Identity. I use the tool just to sign in to different applications that we have. We basically set up Okta Workforce Identity in our mobile phone. We do the scanning part and then enter our official email address and acknowledge that. They will send a code to the mobile phone. Once that code is authenticated, we are good enough to use that tool going forward. That's the initial setup we do on Okta Workforce Identity.

Okta Workforce Identity is really useful because all internal users that we have in our transfer server have now moved to it. In the progress, it's a suite, as it's a part of MOVEit Automation as well as MOVEit Transfer. On the MOVEit Transfer, all internal users in our company have moved to Okta Workforce Identity single sign-on option. The benefit was addressing issues where people were using incorrect passwords. When they continuously put incorrect passwords, their IP would get locked and their account would get locked. Additionally, there were very few users who kept passwords in secret tools or KeePass tools. Most of them were putting the passwords either in mobile phones or in OneNote or text documents where the data could get breached easily. To deal with all these issues, Okta Workforce Identity is a perfect tool where internal applications can be signed in using your authentication tool itself. It functions as two-factor authentication.

I am using Okta Workforce Identity for login purposes only.

View full review »

I started using Okta Platform when I led a team to build software and we encountered security issues. We were looking for the best SSO software platform that we could integrate into the system, and during my research, I came across Okta Platform. I have used it for the current system I am building, and I am currently using it to help with the SSO integration flow and MFA.

I use AWS to access Okta Platform.

Okta Platform provides centralized identity, which is one of the major benefits. For example, I use AWS, but if I want to access Okta Platform, my login details for AWS are not needed. Using it for building systems for customers allows companies to access their systems seamlessly through the same procedure, which makes the workflow easy for them. One of the things that helped us was implementing role-based access. One of the systems I built and led the team to develop was a super admin dashboard that extends through a complete chain. We were able to use Okta Platform to manage roles, and this is one of the key areas where Okta Platform has helped me significantly.

Okta Platform helps me secure access to cloud infrastructure, APIs, and containerized workloads. I have not integrated with AI before, but in terms of app redirects and the systems involved, when a user tries to access their application, there is a redirect to Okta Platform, and then Okta Platform verifies the user. That is how my workflow functions. My first application was supported by this architecture, and studying Okta Platform helped me develop that architecture because my previous architecture was not effective. I learned to have users access the application and then get verified by Okta Platform, which provides the token for them to gain access to the system. I believe this uses SAML, and it really works well for us to accomplish all of that.

I have not tried using Okta Platform to protect non-human identities in my environment, such as service accounts, machine-to-machine access, or AI agents, and I have not explored that area.

In the current system I am working on, which is one of the biggest and most complex projects I have completed, Okta Platform helps me address industry and regulatory requirements. The way the system is structured with user data, funds, and role-based assessments, my greatest satisfaction is that I can use Okta Platform to seamlessly manage all of this. Going forward, if I can use Okta Platform in AI and explore AI integrations, I believe I will be very satisfied.

View full review »

Our main use case for Okta Customer Identity is that all of our in-house applications are under Okta. A user or customer has to log in to Okta Customer Identity and then they can access the application. It serves as our main SSO application which we are using.

View full review »

In my current job, we do rely a lot on Okta Platform but we are not using some more advanced features from them; we have some basic subscription with Okta Platform regarding the single sign-on product they offer.

In both my previous job and in this one, we are using it as our main identity provider for our employees to log in into as many apps as possible with it, just to keep things as secure as possible and provide a good employee experience. Instead of our employees having to remember a lot of passwords and credentials, they rely on one single Okta Platform account to access as many systems as possible.

We are not relying on Okta Platform to secure access to cloud infrastructure, APIs, centralized workloads, or AI/GenAI services in our architecture at this time. I know there are ways to leverage Okta Platform for securing APIs and servers, but we mostly rely on Okta Platform for human access.

We do have some service accounts that we rely on, but I wouldn't say we are using more advanced features from Okta Platform. We do use those service accounts to integrate with other platforms, but I understand that the question was mostly about more advanced features from Okta Platform.

Both in my current job and the previous one, we were in Fintech companies in the financial space. One of the reasons to go with Okta Platform is because they are a well-reputed company, providing some attestations such as SOC 2. We try to go with a reliable, reputable company that other companies in the same space tend to choose, so it's a no-brainer to go with Okta Platform.

View full review »

My use case for Okta Platform is that we mostly use it for SSO for the applications we have integrated with Okta. We primarily use SSO for user authentication, and user management is not particularly involved, but we are importing users from Active Directory to Okta.

I assess the role of Universal Directory as a single source of truth for our user identities by stating that there is an application called Workday, and from Workday to SailPoint, Okta Platform will be the target system for SailPoint. When a user joins the organization, aggregation runs from HRMS to SailPoint, which is responsible for creating the birthright application, with AD being one of those. Once the user is created in AD, import jobs will run based on the mapping we did with AD and Okta Platform, and the user will be created in Okta Platform.

View full review »

Okta Platform is essentially the gateway for everything we do. We have the Okta app on our phones and computers, and it is the only way we can access any of our interfaces on a day-to-day basis, including work messaging on Slack or any of our apps. We go through Okta FastPass to gain access. Every 60 days, I have to reset that on my phone by logging out of everything, doing Face ID, and verifying my credentials before I can log back in and keep everything secure. Additionally, we have to update our password every 180 days or so. I basically start my day every morning with Okta identification or verification.

Okta Platform helps to secure access to cloud infrastructure, APIs, containerized workloads, and AI generative AI services. It pairs well with some of the AI tools we use. I even have a verification method for ChatGPT and Glean, which is another AI interface. Okta Platform essentially applies to anything I use on a day-to-day basis. I do not get any pop-ups throughout my day, which indicates that it is securing the interface or network I am using or even just the application.

Okta Platform protects our benefits and payments app through Workday, so it definitely protects my benefits, my pay information, and any type of personally identifiable information such as first name, last name, and Social Security number.

View full review »

I have been using Okta Workforce Identity for single sign-on purposes to identify and authenticate my identity and access resources at AWS. Whenever I want to connect to Amazon Web Services, I provide a particular CLI Okta command, which opens a window where I am redirected to Okta Workforce Identity's single sign-on page. I authenticate myself through mobile, and once that authentication is completed, I am able to access a particular account according to the role that I have configured in the CLI command.

View full review »

We are providing identity access management to the customers with Okta Customer Identity, and then application integration, user onboarding, and related functions.

I'm a senior consultant using Okta Customer Identity.

We are the implementers of Okta Customer Identity as users.

View full review »

The main differences between Okta Platform and Cisco for the IAM solution are that Okta Platform does not have an exclusive product that is tagged federal, and it depends on the person who is deciding it. The way I made Okta Platform comparable with Duo Federal is by attaching it to CAC, which is used by the military.

View full review »

My job title at FNTS is Senior Security Analyst.

I have been using Okta Platform for three years.

My main use case for Okta Platform is multifactor authentication.

For multifactor authentication in my organization, to log into specific sites, we need Okta Platform as a multifactor authentication to get in.

The process has made logging in easier and more secure for me and my team.

View full review »

Okta Platform is my primary tool for implementing Single Sign-On and Multi-factor Authentication. I use Okta Platform primarily for securing employee access, along with leveraging it for lifecycle management to automate user onboarding and offboarding.

View full review »

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.

View full review »

My use cases for Okta Platform involve having a single place for authentication, as my company requires it for all of our applications that we use with our organization, which includes SAML and SSO. It's a critical piece for authentication, and the token generally lasts about eight hours based on our company's configuration, allowing us to sign in once a day and eliminating the need to enter credentials multiple times for different applications. Okta Platform authentication is essential because it minimizes the hassle of signing into multiple applications while maintaining security. Essentially, all my critical apps are secured with Okta Platform, which also provides features like second-factor authentication through cell phone verification or facial recognition. Overall, it's very functional and an integral part of our business processes.

Regarding how Okta Platform helps secure access to cloud infrastructure, APIs, containerized workloads, or AI services in our architecture, I can't provide an authoritative answer on how security is hardened since I wasn't involved in that aspect. However, I know that it provides security. My company has been using it for four years without plans to change because it remains secure, even as we increase our internal applications and expose some to clients.

The workloads secured by Okta Platform are hosted across multiple cloud providers, including AWS, Azure, and some GCP, so it encompasses all of those.

For AWS, we have integrated EC2 instances with Okta Platform, and I'm not sure about other services or buckets related to the things you mentioned, such as Amazon Voice.

View full review »

One of the majorly used use cases for Okta Workforce Identity is the assignment of different SaaS applications, which are cloud-based, and using them with single sign-on. Users don't have to remember the password for each and every online cloud-based application. They just need to sign in with one email and password. This is one of the major benefits of using Okta Workforce Identity.

View full review »

My main use case for Okta Platform is single sign-on.

As a specific example of how I use Okta Platform for email sign-on in my organization, we log in to our browser and then enter our username and password, and then we receive a Google Authenticator code, a six-digit code which we enter, and then we can log in.

View full review »

Okta Platform serves as a single sign-on tool in our daily operations. We use Okta Platform because we have access to numerous applications, and it is impractical to add all websites to a favorites bar or remember all the passwords for these applications, tools, and websites. We have configured Okta Platform for every person, allowing them to connect to the tools and applications through single sign-on.

View full review »

As an integrator, I work with Okta Platform.

Okta Platform can be used for IAM and IGA; it is a cloud-based solution for Identity and Access Management, as well as Identity Governance and Access.

As an integrator, I find Okta Platform user-friendly with a good number of connectors, making it easy to integrate with applications, and it is easy for SSO implementation and MFA implementation.

Lifecycle Management is configurable in Okta Platform; you can configure the joiners, movers, and leavers process with this product.

View full review »

We are currently using Okta Customer Identity as a managed service platform. We are building a platform where our customers can subscribe to different products of Okta Customer Identity, such as Access Manager, Entity Manager, and Okta Privileged Access. Our customers purchase subscriptions and create a PO number, which we use to perform technical implementations. View full review »

We are an advertising company with around 400 employees in four different countries: Peru, Chile, Mexico, and Brazil. We have implemented Okta Customer Identity to enforce security in our applications and ensure all users access them securely. We use Okta Customer Identity for various applications like Office 365 and several other applications essential to our business.

View full review »

It is for Single Sign-on and Multi-Factor Authentication.

View full review »

Customers' workforce often operates within multiple scenarios and setups. For instance, some customers may use Microsoft Active Directory. For example, out of 5,000 employees, only 2,000 might be integrated into AD, while the rest could have access managed directly within specific applications by their respective owners. Users are burdened with managing multiple usernames and passwords, needing to input both separately whenever accessing an application. Moreover, there's a lack of visibility regarding which users possess privileged access, and whenever users change roles, it becomes challenging for customers to update access across various application layers due to the absence of centralised control. To address these issues, Okta Workforce Identity offers a solution. By consolidating identity and access management into a centralised repository, it streamlines access control, providing users with appropriate access levels based on their profiles. This centralised approach simplifies management for customers, enhancing security and efficiency.

View full review »

We use the solution for authentication purposes to access our applications.

View full review »

I work for one of Norway's largest employers with 50,000 employees. This is Norway's largest retail chain and we use it for 30,000 workers in retail, 15,000 in warehousing, and 5,000 in the corporate environment. For all of these, onboarding is automated to the HR and we have an old CA, which is now called the Broadcom Identity Management Solution for provisioning into Okta Workforce Identity. In this solution, we take those 50,000 identities and we've now built a B2B portal so that vendors, producers of the stuff that is sold in these retail chains, can log on and do things like plan their shipments, have the accounting done, et cetera, et cetera. So there are about maybe 20,000 people, a total of 70,000 people in this identity space. Last but not least, is the PAM solution. So we have maybe 300 IT staff on shore and we have maybe 600 offshore. I haven't done the latest count, but around 1000 IT workers authenticate through Okta Workforce Identity but are then given access to the PAM solution because the PAM solution protects both our cloud environment and our on-prem environment. We use the cloud to get into the on-prem.

View full review »

We use Okta for identity and access management for our internal services, cloud services or applications (SaaS). We have a hybrid setup since we have a global workforce, so we unify our IAM services.

View full review »

The solution is used to eliminate a VPN, provide identity authentication, and single sign-on (SSO). We use Zscaler authentication to manage endpoint logins, endpoint report management, and single sign-on for applications.

View full review »

We used the solution for domain control and password management. In my previous company, they had 40 different products. We used Okta for single sign-on management.

View full review »

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.

View full review »

I use the solution in my company for its single sign-on capabilities and for secure authentication.

View full review »

I am just an end user of the product, so I don't know how the product is used in remote force management in our company. I use the product to help me log on to our company's security systems.

View full review »

Okta Workforce Identity stores all your applications in a portal. It saves passwords, eliminating the need to remember them. In addition, we use 1Password as a backup in case someone forgets their password.

View full review »

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.

View full review »

I use Okta Workforce Identity in my company since it supports single sign-on (SSO).

Okta Workforce Identity is good for helping control all applications in one console.

View full review »

Okta provides island access management solutions, which means that anyone who needs an IIM solution can get it through Okta. For example, if you have 30-40 applications and users that need to log in to all of them, Okta can integrate all of the applications into a single point of access where users can log in once and use the same session for all of their applications. Okta also provides multi-factor authentication and other security policies to protect your users and applications.

View full review »

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.

View full review »

We use it for API authentication, on-premises clusters as well as cluster access, and cloud cluster access.

View full review »

I work for a review website for enterprise IT. We publish reviews for other people to read, either publicly or anonymously. We also work directly with Okta Platform, and they are interested in user feedback regarding what people like and what people dislike about their product. I am actively using Okta Platform.

View full review »

We use the product to manage access and identify several applications.

View full review »

We use Okta Workforce Identity for single sign-on (SSO).

View full review »

We use the solution to give access to the server. It verifies and allows users to access the server.

View full review »

We used Okta Workforce Identity for SSO, MFA, life cycle management, as well as the external identity and access management for external customers. We used the solution internally for accessing all applications, so we had an Okta software portal where we could then start any application we wanted.

View full review »

I am using Okta Workforce Identity for identity access management.

View full review »

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.

View full review »

Okta has recently built Okta Identity Engine (OIE). It has a lot 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.

Scalacity was a company acquired by Okta, and its technology was integrated into Okta's Advanced Server Access (ASA) product.

View full review »

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.

View full review »

We are primarily trying to uncover the differences between this product and JumpCloud. 

View full review »

We use the solution for our single sign-on applications. It resolves password issues.

We use it for authentication and 90% of our SaaS app. 

We use it for on and off-boarding users. It syncs with our on-premises master directory to set them up and take them off.

View full review »

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.

View full review »

Workforce is used to both manage our identities with multi-factor authentication for the users and it's also used to handle workflow, so onboarding and offboarding, et cetera.

View full review »

We've been using this solution for SSO and consolidation of IDs.

View full review »

The primary use cases are SSO, user management, and SSO integration with various cloud services, including AWS, GCP, GitHub, etc.

View full review »

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.

View full review »

We have been using this tool for access management. Our client has connected their app's security with Okta Workforce Identity. We have used LinkedIn's libraries to integrate it with various apps, including Oracle and others.

View full review »

Our organization only uses Okta for single sign-on. Everybody is working from home, so we need a multi-factor authentication solution for remote users. We have around 70,000 users. 

View full review »

We are using Okta Customer Identity for single sign-on. For example, if there is an organization that wants to have a user use one credential, user name, and password, and log into multiple applications. Then in that case you can use the Okta Customer Identity single sign-on tool.

View full review »

We are using Okta for authentication. It provides identity. We are using it as an identity provider. Single sign-on is the primary use case here. We use it for our customers and our employees.

View full review »

Okta Workforce Identity is used for MFA and SSO and it satisfies application authentication.

View full review »

We implemented this solution for all employees within our environment. So, the entire single sign-on is through Okta for all of our employees through all applications.

View full review »

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.

View full review »

We use this product to control access to applications.

View full review »

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.

View full review »

My primary use case is to have a single sign-on and to have identity access management. I'm the team management manager and we are customers of Okta. 

View full review »

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.

View full review »

It is the authenticator for secure logins. We use it to log into companies' applications with a double security level. 

It is to prove that I am an employee authorized to use certain applications.

View full review »

We are using Okta Workforce Identity for our clients to be able to plug into the applications without entering the credentials. We are using a single sign-on for our services.

View full review »

I did about six months' worth of work on it. It was more towards getting our lab set up, getting the certification done, etc.

View full review »

The primary use case is for identity and access management. The single sign-on and access control can be done as a part of Okta. You have APIs to work within Okta and user provisioning.

View full review »

We are using Okta as a service where users can access our services that are maintained in the cloud or on other websites.

View full review »

Okta essentially helps us to onboard employees. We do have difficulty onboarding specific employees, as we're a growing company. Okta helps us provision the software as a service applications that we have in our company for the new hires. We do about 5% software as a service application. Once they join the company, it's a simpler process and a quick onboarding process for them.

View full review »

The main use for the solution is for security. It can provide multifactor authentication to allow more security when accessing server applications or different types of services.

View full review »

Our customers use it for multi-factor authentication, lifecycle, and workflow.

View full review »

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.

View full review »

The primarily use of the solution has been for education and to support our Federation identification as well. We also use it for a Google IDM, in that you use it to segregate our Google DCB environment and provide for our engineers.

View full review »

We are an authorised reseller partner

View full review »

We are a solution provider and Okta is one of the products that we implement for our clients. I am a solution architect and help to design the system.

Most of our clients have a hybrid architecture where they want to use a single sign-on. They have some applications on-premises, whereas others are on the public cloud. This means that they have a two-tier or three-tier architecture.

View full review »

We mostly use it for MFA for logging into our Windows RDS environment and a web-based application called Tableau. We are using the latest version.

View full review »

It has got a big network of apps that easily integrate into it, making deployments a lot faster than traditional identity platforms. So, the use case will be companies that are looking to be on a cloud journey for cloud adoption strategies. It also suits companies that have on-premise applications and would like to make them web-based, essentially, access them on one portal. Thus, allowing companies to ensure that they can pretty easily manage access to these applications by their users.

View full review »

We are using this solution for access management and user provisioning. We are also using it for user and group synchronization and as a password for authentication.

View full review »

SSO and MFA: To extend Identity Authentication on the existing IAM identity and account operations to the multiple domains for administrative and help desk personnel. Improve consistency of the identity management processes across the organization and improve compliance with governance mandates.

The access management with Okta revolves around the establishment of a single authentication store (reducing the number of accounts), which will allow the migration of existing applications to federations, or a common identity store. It will also establish a suite of centralized authentication services that can be used for future applications and systems platforms.

View full review »

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. 

View full review »

The primary use case of this solution is for access management, multi-integration, and passwordless access.

View full review »

We primarily use the solution to access cloud solutions and VDI. 

View full review »

• 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.

View full review »

We use it as an SSO hub for applications to be added/removed from users' profiles and troubleshooting, as well as an active directory. 

I work at a service desk providing IT support to PayU international and Naspers.

View full review »

We used this solution for provisioning more than one and a half LAC users and integrating more than 300 applications. SSO and MFA has been implemented on almost all applications. MFA options used: RSA token, Okta Verify, etc.

View full review »

Okta is not just an identity provider (IdP) since, with the help of SAML, it can also be a service provider (SP), which then allows it to integrate with a different identity provider. In other words, it provides SSO. In my organization, we use Okta as a centralized solution for our multiple platforms. With just one login users are able to access any associated platforms without having to log in multiple times.

View full review »

We use Okta primarily for user-provisioning and as an SSO portal for access to our applications.

View full review »

• SSO integration with an on-premise Active Directory environment
• Universal Directory synchronization and leverage UD to integrate with other cloud federated applications
• O365 SSO integration

View full review »

We use Okta for single sign-on (SSO) of multiple applications, access management, and multi-factor authentication (MFA).

View full review »

As an Okta Identity engineer, I implement Okta for different clients such as banks, telecoms, and insurance companies. These companies need an IAM solution to manage their employees securely and provide them with access to the right applications. Okta is used to automate provisioning and support any errors encountered during and after deployment. 

Companies use Okta Workforce Identity to manage their employees' secure access to applications and to minimize the effort required by IT teams to manage identities. The solution helps organizations allow their employees to log into their applications without re-entering credentials and securely access their applications via MFA.

View full review »

I mainly use Workforce Identity to give users access to applications.

View full review »

We use the solution for application security.

View full review »