Migrating your AppZen SSO to Okta-federated identity

Introduction

AppZen is deprecating its internal SAML integration. Customers whose tenant currently connects directly to AppZen are being migrated to Okta for federated identity. This article explains what to expect and how to prepare.

What AppZen will ask you for

To coordinate the change with your team, AppZen asks for:

1. The appropriate technical contact on your side (IT, Identity, or Security).
2. The identity provider (IdP) you use today, for example Okta, Entra ID, Ping, or ADFS.

Having this information ready helps the migration go smoothly.

Supported SSO type

AppZen supports Service Provider (SP)-initiated SSO only. Users sign in from the AppZen sign-in page by clicking Login with SSO.

Complete the setup yourself

A user with System Admin access can complete the SSO setup in the AppZen UI. You do not need to wait for AppZen Support to do this.

1. Upload the metadata file from your IdP into AppZen.
2. After the upload, AppZen generates the Assertion Consumer Service (ACS) URL, the Audience URI, and an AppZen metadata file.
3. Use these values to configure AppZen in your IdP.
4. Test the connection by clicking Login with SSO on your AppZen sign-in page. The test user's User authentication must be set to External.

If you cannot provide a metadata file yet, contact AppZen Support. The SSO Setup & Troubleshooting Guide describes how a placeholder metadata file can be used to generate the correct one from your IdP.

For full step-by-step instructions and error troubleshooting, see:

• SSO Setup (Expense Audit)
• SSO Setup (Autonomous AP)
• SSO Setup & Troubleshooting Guide

Need help?

If you have questions or need assistance during the migration, submit a Support Request and the AppZen Support team will help.