Loading…
Okta
Identity and access management company providing authentication, authorization, single sign-on, and identity security solutions.
- 68 posts summarised
- latest
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
From their blog
Latest articles
How to Get Going with the On
This workshop setup guide prepares a minimal Todo SaaS application for a series of enterprise-readiness workshops, while warning that the base app is not production quality and has intentional security shortcomings. It uses a React frontend, an Express API written in TypeScript, SQLite persistence, Prisma for ORM and database visualization, and an Nx workspace for shared project commands. Developers install Node.js v18 or higher, obtain the repository, run npm ci, seed two users with npm run init-db, and start the application with npm start. The frontend runs on localhost:3000, the API on localhost:3333, and Prisma Studio on localhost:5555 for inspecting users and todos. The guide concludes by directing developers to workshops covering OpenID Connect, SCIM, Terraform, Okta Workflows, and cross-application sign-out.
How to Take Your Enterprise
This installment in a Devday23 presentation series addresses how to move an enterprise-ready SaaS application beyond its MVP. It focuses on the functionality needed to help an application stand out to enterprise customers, including user provisioning and automation that can scale. The stated goal is to support growth from a working MVP toward enterprise adoption. Aaron Parecki shared material on Okta Workflows, provisioning, SaaS application maturity, and SCIM, with links to a SCIM developer video and Workflow Connector Builder tutorials. The broader series also points to upcoming coverage of authentication mechanisms and deployment automation, positioning enterprise readiness as an ongoing progression rather than a single feature.
How to Build an Enterprise
Enterprise customers want employees to use a centralized authentication process called Single Sign On (SSO). This post introduces an enterprise-ready Devday23 presentation series focused on what enterprise readiness means, what enterprises look for, and how to build an enterprise-ready MVP SaaS application. Its identity-focused material explains the role of SSO in SaaS applications and points readers to Dan Marma, Product Acceleration Principal Architect, for the “Single Sign On (SSO) in your SaaS applications” presentation. The series will also cover moving an application beyond identity MVP toward elevated authentication mechanisms in later posts. It invites questions and continued content through Twitter and YouTube.
How to Add Authentication to .NET MAUI Apps
This tutorial shows how to add Okta-based authentication to a .NET MAUI application, covering project setup, OpenID Connect configuration, sign-in, sign-out, and platform integration. It uses IdentityModel.OidcClient, an OktaClient wrapper, an OktaClientConfiguration class, and a WebBrowserAuthenticator implementation to connect the application to Okta’s browser-based authorization flow. The walkthrough creates a native OIDC client with the Okta CLI, registers redirect and logout URIs using myapp://callback, configures dependency injection, and updates the UI to display claims after login. For Android, it adds a WebAuthenticationCallbackActivity with an intent filter for the myapp scheme and enables Custom Tabs visibility in AndroidManifest.xml. The post includes troubleshooting for NuGet configuration and runtime-pack errors, but notes that the Okta CLI was deprecated and the original instructions no longer work exactly as written after the May 2025 plan change.
What Enterprises Look For: Devday23 Enterprise Customer Perspectives
Moving a SaaS application from B2C or small-company B2B customers to enterprise customers raises questions about whether enterprise buyers have different expectations. This installment of the Devday23 enterprise-ready presentation series focuses on what enterprises look for when selecting SaaS applications, with particular attention to identity and how customers would use the application. The WIC Devday 23 virtual conference addressed the topic through a presentation by Jon Lehtinen, director for “Okta on Okta” products at Okta. The broader series also covers enterprise readiness, authentication considerations, user management, authentication mechanisms, building an enterprise-ready MVP SaaS app, and taking that app beyond MVP, while the supplied text does not provide the presentation’s specific answers or conclusions.
What Does It Mean to Be Enterprise Ready: Devday23 Keynote
What makes a SaaS application ready for enterprise customers when identity is involved? This Devday23 keynote introduces enterprise readiness as a concern spanning application security, user onboarding, scalable authentication, identity, user management, and automation. Arnab Bose, Chief Product Officer for Workforce Identity Cloud at Okta, leads the presentation’s “Why” and “What” questions in a half-day virtual conference hosted at WIC Devday 23. The keynote is positioned as the opening of a series covering enterprise customer expectations, building an enterprise-ready MVP, moving beyond MVP, authentication considerations, user management, and stronger authentication mechanisms; a related “Setting the Bar for Enterprise-Grade Identity” whitepaper provides benchmarks for secure SaaS management.
Unlock Identity Expertise with Our New Developer Podcast!
Okta’s Workforce Developer Advocacy Team has launched a monthly Workforce Identity Developer Podcast for education about identity and development for customers using Okta as their identity provider. The first highlighted episodes cover Workforce Identity, security history, phishing-resistant MFA, and the relative benefits and drawbacks of WebAuthN and Passkeys; another compares OAuth application integrations with older SSWS tokens. A further episode discusses building SaaS for enterprise customers, including the “Enterprise-Ready MVP,” broadening “Okta Developers” to people building code for Okta customers, and extreme enterprise use cases. Audio is available on Casted, while new content and feedback are supported through social channels, YouTube, and comments on the developer forum.
Supporting Devs Through Advocacy
Semona describes her transition from Okta Developer Support Engineer to Developer Advocate after three years supporting admins, developers, Independent Software Vendors, and partners integrating with Okta workforce products. Her earlier work included OpenID Connect, OAuth 2.0, external and social identity providers, SCIM, OIN App Submission, Okta SDKs, the Okta Sign-in Widget, Token Inline Hooks, and Terraform, while cross-functional alliances connected her with Customer Success, Product, Engineering, Solutions Engineering, and Architects. She saw support cases as a way to understand developer problems and collect feedback that could inform improvements. In advocacy, she plans to use that experience to help developers avoid common problems, build community, learn with developers, and advocate for Okta developer community needs, with Python as her favorite programming language.
Topics they write about
All topics →Weekly digest
The best engineering reads, once a week.