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.

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

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.

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.

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

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

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.

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.

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

I am using Okta Workforce Identity for identity access management.

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

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.

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

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. 

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.

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.

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. 

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.

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

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

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.

We use the solution for application security.

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.

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.

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.

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.

We use this product to control access to applications.

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.

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. 

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

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.

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

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.

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

We are an authorised reseller partner

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

• 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

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

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.

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.

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

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.

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.

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.

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.

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

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.