CA SiteMinder Migration Guide

Executive Summary

Securely connecting users to applications is not a new problem. To address this challenge, many organizations adopted CA SiteMinder and supporting services like CA Advanced Authentication, and CA Directory to secure access to on-premise web applications.

With the emergence of new types of apps and use-cases, enabling access to all systems and users broke the CA model, which runs on-premises, is hard to operate and upgrade, requires manual tasks for adding MFA and integrating with SaaS apps, and cannot deliver security cost-effectively.

Okta Access Gateway

Okta Access Gateway delivers Okta SSO and MFA from the cloud to your on-prem web apps, replacing on-prem SSO (CA), complementary servers like CA Advanced Authentication, and the underlying infrastructure, while supporting modern requirements.

The solution has a simple architecture that does not require additional middleware – admin and policy servers – and database – policy and user store – servers to operate.

CA SiteMinder Migration

The migration from CA SiteMinder to Okta is executed in two steps. In the first step, you deploy Okta and deprecate CA SiteMinder while providing universal SSO and MFA for all apps: from ground to cloud.

In the second step, you classify, migrate apps to Okta, and then uninstall CA SiteMinder and supporting servers:

What's Next

For more details on how to migrating from CA SiteMinder to Okta, continue reading this guide.

For a tailored plan on how to migrate to Okta, reach us at www.okta.com/contact-sales

Introduction

Securely connecting users to applications is not a new problem. To address this challenge, many organizations adopted CA SiteMinder and supporting servers like CA Advanced Authentication and CA Directory to secure access to on-premise web applications.

As technology evolved, organizations adopted new solutions that require modern access control. From SaaS, to mobile access, to Infrastructure as a Service, and Single Page Apps (SPAs), s