Okta Platform

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 .

Okta Platform team told us about a feature called Universal Directory. I have tried using it.

Okta Platform performs well regarding stability, lagging, crashing, and downtime.

Okta Platform can be scaled across different applications, platforms, and even for dashboard missions. It performs well regarding scalability.

I have not tried using any alternatives to Okta Platform or similar solutions.

Okta Platform pricing and deployment are easy.

One person can handle the deployment for a new client. Deploying Okta Platform does not require any maintenance on my end.

I do not have any partnerships with Okta Platform; I am just a customer. I will refer Okta Platform if scenarios arise. If anyone asks for a suggestion, I will definitely suggest Okta Platform. I would give Okta Platform a rating of nine out of ten because no software deserves a perfect score, but Okta Platform comes very close.

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.

The best features offered by Okta Platform that stand out most to me in my day-to-day work include Universal Directory and profile mapping, which matter as they form the foundation for clean attribute-driven access. I can normalize identities from HR and AD, map attributes once, and drive consistent entitlement across apps.

Additionally, features including group rules, dynamic assignments, SSO with robust protocols supporting SAML and various OIDC integrations, excellent provisioning, deprovisioning capabilities, adaptive MFA, WebAuthn, and efficient system and troubleshooting tools also stand out.

Universal Directory and profile mapping help me with day-to-day identity management by serving as the backbone for keeping identity data clean, consistent, and automation-friendly. Practically, Universal Directory acts as a single source of truth for users, allowing us to aggregate attributes from HR, Workday, AD, and other sources into a single Okta Platform user profile. This normalization standardizes formats, such as email in lowercase and phone numbers in E.164, preventing downstream apps from breaking due to case sensitivity or formatting.

Profile mapping enables me to transform attributes once, such as concatenating first.last for usernames, deriving different manager emails, and reusing them across all apps. This creates clean, predictable attributes driving group rules, which in turn govern app assignments and SCIM provisioning, making the JML process work efficiently without the need for tickets.

Okta Platform Integration Network's capability to enable faster deployments serves as a force multiplier for speed and risk reduction when it is mature and well-curated. It essentially turns a lot of custom work into configuration, which results in gains in deployment speed and reliability.

I assess the role of Universal Directory as a single source of truth for user identities in my organization as central to how we enforce identity hygiene and drive automated access. Its role functions as an authoritative profile and policy engine that normalizes identity data and pushes clean, consistent attributes downstream. We utilize it for data aggregation, normalization, profile mapping and precedence, attribute-driven access, federation claims, and policy enforcement. The measured outcomes with Universal Directory in the middle indicate that onboarding lifecycle durations dropped by more than 30 to 40%, with late access-related tickets falling by the same percentage, around 35 to 40%.

Although I am a fan of Okta Platform overall, there are areas where it could improve security outcomes and reduce admin friction. My top improvement areas include the system log and analytics upgrade, which are great for point troubleshooting, but trending and root cause analysis across large tenants still require exporting to SIEM . Verbose queries and long-range retention costs can add up. Additionally, while certificate rotations are better than most, the process is still manual for busy portfolios, especially concerning multi-SP SAML certificate rotations and app metadata drift.

Two more buckets of potential improvements for Okta Platform involve user experience and security. There is the issue of push fatigue and prompt sprawl, where users receive multiple prompts across different apps and sessions.

I arrived at the rating of eight because the core controls are strong and reliable, but a few operational UX and UI gaps prevent it from being rated higher. The reasons for not giving it a nine or ten include ongoing issues concerning safety and change safety, the complexity of group rules and mappings, and the lack of robustness in policy management. Additionally, there remains a need for more manual involvement than necessary, especially for large portfolios and dual certificate rotation, along with proactive SP data metadata validation.

I have been working in my current field since April 2023, with a little over three years of experience in that time.

Okta Platform is stable on an enterprise scale; however, scalability ultimately depends on how one architects and operates the system.

The scalability of Okta Platform is impressive, but its effectiveness relies on how integrations are designed, rate limits are handled, and day-to-day operations are managed. Customer support is generally reliable, featuring clear tiers with excellent assistance during roll-outs if the right plan is chosen and SLAs are well defined. Best outcomes emerge when paired with strong internal runbooks and partner support.

Overall, customer support tends to be dependable, but the real experience will depend on the support tier selected and the level of preparedness.

Before adopting Okta Platform, we utilized a homegrown SSO system employing ADFS for certain apps and direct LDAP binds for others, alongside a few apps with local accounts.

Automated lifecycle management has transformed my onboarding and offboarding efficiency significantly. Previously, onboarding felt toward a bottleneck, and offboarding raised risk concerns. Before implementing the Okta Platform-driven lifecycle, HR would create a ticket in ServiceNow , and three different teams would manually provision AD, email, and six to eight SaaS apps, which typically took around one to two business days, during which errors frequently occurred, including wrong groups and missed deprovisioning, resulting in no clean audit trail.

Offboarding was even worse, with terminations after hours sitting until the next day, creating 12 to 24-hour orphaned account windows across key apps. The task was to automate the entire JML process end-to-end. After integrating Okta Platform and linking HR to serve as Okta Platform UD, mapping everything, and designing attribute-driven access with SCIM provisioning while implementing movers logic, the results were remarkable. The time-to-access dropped from one to two days down to two to four hours for SCIM provisioning, improving day-one readiness from 78 to 96% for new hires. Manual provisioning tasks fell by 55%, allowing the IAM  team to reclaim 10 to 12 hours per week to focus on governance and SOD areas.

This transformation allowed HR hires in Workday to auto-create the Okta Platform user, with Universal Directory attributes driving the assignment seamlessly.

My impression of the automated threat response feature in Okta Platform AI is that it brings net positive results concerning both speed and containment when tuned appropriately. It shortens the time from suspicious signals to protective actions, practically reducing risk without overwhelming the SOC with noise.

We have seen a return on investment with clear metrics that demonstrate both hard savings and reduced risk.

Pricing for Okta Platform has proven to be straightforward, with no challenges encountered. As a fully SaaS solution, everything is pre-built and managed by Okta Platform. The costs come down to paying for subscriptions, professional services, and ongoing operations, specifically licensing workforce identity with SSO and adaptive MFA for all employees, along with add-ons towards Lifecycle Management for JML automation at scale, Advanced Server Access for Linux and Windows servers, and IGA  for access certification indicating SOD. The pricing per-user list drops when user counts rise and with multi-year commitments.

In evaluating options prior to choosing Okta Platform, we ran a structured assessment comparing various solutions such as ADFS, Duo plus manual JML, and also considered alternatives including Microsoft Entra ID  and Ping Identity.

My advice for teams considering Okta Platform is to start with clear objectives and metrics, defining what success looks like to ensure effective implementation. I am providing this review with an overall rating of eight.

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.

The best features of Okta Platform include the import feature, which allows for new employees joining the organization to have their AD account created, and when this import runs from AD to Okta Platform, this employee will be created in Okta Platform. This feature represents automation between Okta Platform and AD.

Apart from these features, I appreciate that there are password policies and authentication policies or network zones we can configure in Okta Platform. If we want to restrict the users from logging in from specific network zones or blacklisted ones, we can configure those.

The context-aware policies of adaptive MFA influence my authentication process because we can enable more MFA based on client requirements. Okta Platform is one of the MFA tools available, alongside others such as RSA, and based on the requirements, we can enable those and apply the policy accordingly.

The positive impact I have seen from using Okta Platform is that it makes it easier for new joiners to get birthright access and have users added based on department or employee type. We implement rules and policies, such as when a user joins the sales department; we can configure the group rule, and the user will automatically be tagged to that specific group. This represents an automated process with Okta Platform, rather than doing it manually.

The automated lifecycle management helps with the efficiency of onboarding and offboarding by ensuring that once a user joins the organization, they come into HRMS. From there, it goes to AD, and the target will be Okta Platform. Birthright access and applications are provisioned based on conditions. For offboarding, if an event is triggered, such as leaver or termination, values will be populated in AD, and once the import runs, Okta Platform will terminate the user, disabling access and removing whatever accesses the user had.

In Okta Platform, I do not see much room for improvement because currently, they are managing automations and the new workflow, which helps with automation. Previously, this was not available in Okta Platform, but it was introduced recently.

The automation aspect can be improved.

I have been using Okta Platform for three and a half years.

The stability of Okta Platform, I would say, is an eight because it is growing day by day. Previously, it had static features without automation, but currently, it is moving towards automation and introduced workflows.

I would consider the scalability of Okta Platform to be a six.

The scalability rating of six is due to factors that come with the tenant and the specific elements around that, which I am not entirely sure about.

My relationship with the vendor is as a customer and partner. When we have issues with Okta Platform, we reach out to their support team, and they take care of the issues we encounter.

We do not go through AWS , GCP, or Azure  for Okta Platform; instead, we usually access the Okta Platform support portal to raise our concerns, and the team reaches out to us to resolve those issues, sometimes scheduling meetings as needed.

Before using Okta Platform, I did not really use any other software, but I did consider Entra ID, which is most probably similar to Okta Platform. However, Okta Platform has a user-friendly interface and is easy to use.

The integration aspects include that the capabilities come with modern protocols, making it easier for integration with various protocols and target systems.

Integration capabilities of Okta Platform enable faster deployment, as they support modern protocols such as IDP  and SSO.

I have not used Okta Platform AI, but I need to check on its automated threat response features.

Regarding pricing for Okta Platform, I am not aware of how much it costs because I used to work as a consultant for them, and the licensing details are taken care of by the sales team or others.

The solution requires little maintenance, and I would say it is easier to maintain compared to other IM  platforms such as SailPoint, which had huge coding and infrastructure costs.

My advice to others looking to implement Okta Platform is to definitely go for the software instead of Entra ID, as it offers a much easier and user-friendly UI.