Okta Corporate Blog

Have you noticed that the Okta Angular SDK went fully standalone? There’s no NgModule left to import, no importProvidersFrom wrapper to remember, and the guards are plain functions now. If you’ve been waiting for the SDK to look like the rest of your standalone Angular app, this is the release you were waiting for. In this post, we’ll pick up a small Angular v22 project and finish it.

Executive summary Okta Threat Intelligence (OTI) recently hit a significant milestone: we sent our 10,000th suspicious domain notification to a customer. I wanted to mark the moment by explaining how and why we do this important work. I also want to share some research we’ve done to prove just how unique these notifications are.

If you currently federate enterprise customers using OpenID Connect (OIDC) and want to connect with third-party applications, this Cross App Access (XAA) guide is for you. The Identity Assertion Authorization Grant specification, the basis of XAA, was designed with OIDC in mind. Your app already holds an ID token after sign-in, but it’s the refresh token from that same sign-in that you exchange to reach a third-party app.

It all started with a phone call from an institute that reached out to recruit me for its campus ambassador program. I was navigating my first year of college, figuring things out. It was all new for me, a new city, far from home, and a hostel room. I was not aware of anything except books and lectures. A senior at my campus ambassador program advised me to create a LinkedIn account and start looking for opportunities from day one.

The business impact of identity sprawl Ask an executive how many identity tools their organization runs, and you'll usually get a pause before the answer: Single sign-on (SSO) and multi-factor authentication (MFA) exist in one silo. Identity governance is layered on later. Privileged access is added after a compliance audit. Each tool was acquired for a legitimate reason, but those point solutions weren’t designed to work together.

Your OneDrive version is not supported Upgrade now by installing the OneDrive for Business Next Generation Sync Client to login to Okta Learn how to upgrade Cookies are required Cookies are disabled on your browser. Please enable Cookies and refresh this page. Refresh

What is Okta for AI Agents - Core? Okta for AI Agents - Core is an identity governance solution that has achieved a signed Impact Level 5 (IL5) Provisional Authorization. This milestone extends identity governance capabilities beyond FedRAMP High environments into the Department of War (DoW)’s most stringent tier short of classified systems—where Controlled Unclassified Information (CUI) lives. Why does IL5 governance matter for agentic AI?

What are the benefits of one-time passwords (OTPs)? OTPs offer several advantages for organizations implementing strong authentication: Enhanced security through dynamic generation Unlike traditional passwords, OTPs resist replay attacks and protect against bad actors who might intercept authentication data during transmission. However, OTPs do not inherently prevent real-time man-in-the-middle (MITM) attacks if an attacker intercepts the OTP through phishing.

An enterprise buyer’s framework Key takeaways Evaluating an AI agent identity layer requires looking beyond broad “agent security” RFPs. Our Agent Identity Evaluation Kit provides a checklist, RFI template, and scoring matrix to help you evaluate identity security vendors. To govern autonomous systems effectively, organizations must evaluate identity separately from gateways and observability tools by answering three core questions: Where are my agents? What can they connect to? What can they do?

Executive summary: A new feature, Okta Verify Device Posture Sensor Mode, enables silent MDM deployment of Okta Verify and collects signals across managed macOS and Windows devices. This capability allows administrators to gate Okta Verify enrollment based on device compliance and extend Zero Trust security controls to shared workstations before users authenticate.