# Classic Engine Feature EOL: SSR, Desktop SSO, Device Trust

DevFeed: [Classic Engine Feature EOL: SSR, Desktop SSO, Device Trust](<https://devfeed.tech/articles/classic-engine-feature-eol-ssr-desktop-sso-device-trust-55058.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/09/18/okta-classic-engine-deprecation>)

Author: Vanshika Pandey

Published: 2026-09-18T05:00:00Z

Content type: release

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [okta](<https://devfeed.tech/topics/okta.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Security](<https://devfeed.tech/topics/security.md>), [Device Trust](<https://devfeed.tech/topics/device-trust.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [MFA](<https://devfeed.tech/topics/mfa.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [passwords](<https://devfeed.tech/topics/passwords.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [benefit](<https://devfeed.tech/tags/benefit.md>), [device-trust](<https://devfeed.tech/tags/device-trust.md>), [eol](<https://devfeed.tech/tags/eol.md>), [feature](<https://devfeed.tech/tags/feature.md>), [identity](<https://devfeed.tech/tags/identity.md>), [okta](<https://devfeed.tech/tags/okta.md>), [password](<https://devfeed.tech/tags/password.md>), [passwordless](<https://devfeed.tech/tags/passwordless.md>), [phishing](<https://devfeed.tech/tags/phishing.md>), [policies](<https://devfeed.tech/tags/policies.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [self-service](<https://devfeed.tech/tags/self-service.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [sso](<https://devfeed.tech/tags/sso.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [verification](<https://devfeed.tech/tags/verification.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

## AI overview

Okta will end support for Self-Service Registration, Desktop Single Sign-On, and Device Trust on Classic Engine on March 5, 2027. Organizations must upgrade to Okta Identity Engine to retain those capabilities. Identity Engine provides passwordless authentication, device assurance, phishing-resistant multifactor authentication, and updated security policies.

## Source excerpt

Starting March 5, 2027, Okta ends support for a few capabilities on Classic Engine. Identity and security requirements continue to evolve. Organizations expect authentication experiences that are more secure, flexible, and adaptable to changing users, devices, and applications. Okta invests in Okta Identity Engine, the modern foundation for passwordless authentication, device assurance, phishing-resistant multifactor authentication, and adaptive security policies. By moving to Okta Identity Engine, you access an environment aligned with modern security practices that is stronger, more capable, and built to support how you protect access. What's changing in Okta Classic Engine Here's the full list of affected capabilities: Self-Service Registration Desktop Single Sign-On (Integrated Windows Authentication, or IWA) Device Trust Once support ends, Okta turns off these capabilities on Classic Engine, and you lose access to them unless you upgrade to Okta Identity Engine first. Okta no longer addresses bugs, security vulnerabilities, or broken flows associated with them after that date. Each capability moves to a modern, more secure approach within Identity Engine, where it continues to benefit from ongoing innovation. Why upgrade to Okta Identity Engine Identity Engine gives you authentication capabilities Classic Engine doesn't have, including passwordless authentication, device assurance, and a modernized policy framework built on a newer authentication pipeline. The upgrade itself is free, you get all these capabilities at no additional licensing cost as part of your existing Okta subscription. Identity Engine accelerates five core use cases: Passwordless: Remove password from the sign-in flow entirely, instead of layering a second factor on top of it Phishing-resistant: Close every route to the account, not just the front door. An account is only as phishing-resistant as its weakest enrollment and recovery path. ID verification : Confirm that employees and customers