Identity and Access Management Specialist at a university with 10,001+ employees
Real User
Top 5
Feb 18, 2026
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.
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.
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.
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.
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.
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.
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.
Managing Consultant at a tech vendor with 10,001+ employees
Real User
Top 10
Apr 16, 2025
We are currently using Okta Customer Identity ( /products/okta-customer-identity-reviews ) as a managed service platform. We are building a platform where our customers can subscribe to different products of Okta Customer Identity ( /products/okta-customer-identity-reviews ), 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.
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.
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.
Architect at a tech services company with 1-10 employees
Real User
Top 5
May 2, 2024
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.
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.
Regional Security Officer at a comms service provider with 10,001+ employees
Real User
Sep 6, 2023
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.
Information Technology System Administrator at General Assembly
Real User
Jun 8, 2023
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.
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.
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.
Principle Product Manager at a tech vendor with 5,001-10,000 employees
Real User
Jun 22, 2022
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.
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.
Okta Product Manager at a security firm with 11-50 employees
Reseller
May 24, 2021
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.
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.
Okta Platform provides comprehensive identity and access management, featuring Active Directory Sync, user management, and app auto-provisioning. It ensures security through single sign-on and adaptive multi-factor authentication.Okta Platform offers advanced integration capabilities, allowing seamless connection with in-house and cloud applications. Security features are robust, incorporating multi-factor authentication and SSO to prevent unauthorized access. Users benefit from its ease of...
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.
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.
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.
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.
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.
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.
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.
We are currently using Okta Customer Identity ( /products/okta-customer-identity-reviews ) as a managed service platform. We are building a platform where our customers can subscribe to different products of Okta Customer Identity ( /products/okta-customer-identity-reviews ), 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.
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.
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.
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.
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 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.
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.
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.
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.
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.
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.
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.
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.
The primary use case of this solution is for access management, multi-integration, and passwordless access.
We use Okta for single sign-on (SSO) of multiple applications, access management, and multi-factor authentication (MFA).