Deployment Manager

The Deployment Manager provides a centralized workspace for setting up and managing deployments across multiple environments, such as development, testing, and production. From this screen, you can view all existing deployments, create new ones, edit deployment configurations, add applications, publish updates to your storage provider, and delete deployments when they’re no longer needed.

ℹ️ Where are my Environments?

Environments has been upgraded to Deployments. All of your data and settings have been migrated to this new experience.

Deployments List

To view your list of deployments, go to Deployments on the left sidebar.

• Create a new deployment by clicking Create.

• Edit a deployment by clicking the row.

• Delete a deployment by clicking the context menu (⋮) next to the deployment and select Delete.

  • There is a 30 day retention on deployments. To manage deleted deployments, toggle Pending Deletion and  click context menu (⋮) next to the deployment. From there, you can choose Restore or Permanently Delete.

Deployment Editor

When creating a new deployment, a set of defaults are provided for publishing a configuration for local development. To edit any of the settings, click the Edit buttons next to each setting. A slide drawer appears for each setting.

General Settings

Applications

You can manage the applications in your deployments.

To add an application click Add. From the slide out drawer, select the applications you wish to deploy and click Save.

Please note

A user flow must be configured for OIDC and SAML apps. OIDC apps may require an OIDC provider.

Additionally, you cannot deploy applications with the same name.

To edit an application or user flow, click the name. To remove an application, click the (x) icon.

Host Environment

The Host Environment section enables you to set up the orchestrator host environment, connect to a storage provider, and configure observability settings.

Configuration Storage

To select and a configure a storage provider, click Edit. Select your storage provider, enter the configuration details and click Save. Follow the Storage Configuration Guides to configure a remote storage provider to serve as the destination for your Maverics deployment configuration.

Download Orchestrator Services

Orchestrator services can be installed on Windows, Red Hat Linux, Ubuntu, Docker, and Mac OS (development purposes only). Evaluation Bundles are available when you have selected Maverics Storage as your storage configuration provider.

To download Orchestrator Services, click Select Download. From the slide-out drawer download the package that corresponds to your platform.

Public Key

Configuration bundles published by the Maverics platform are cryptographically signed to ensure their integrity and authenticity. An orchestrator will only load a configuration bundle if it can successfully validate the signature using the public key associated with that specific deployment. To enable this validation, you must set the appropriate environment variables on the orchestrator host. Refer to the Storage Configuration Guides and the Orchestrator Remote Configuration section for detailed instructions on how to configure these settings properly.

To download the public key, click Download.

Orchestrator

The Orchestrator settings section defines how the orchestrator behaves at runtime and governs core operational aspects of session management, identity protocol handling, and caching.

• Under Session and Cookie, you can configure key parameters such as session timeout, idle duration, cookie size, and domain, ensuring consistent user session control and secure cookie handling.

• The Single Logout (SLO) configuration defines the logout endpoint and post-logout redirect URL, enabling orchestrators to manage coordinated logout flows across federated applications.

• In the same section, the OIDC Provider and SAML Provider settings define how the orchestrator responds when acting as an identity provider for applications using those protocols. These settings include metadata endpoints, token URLs, and logout URLs required for standards-compliant identity transactions.

• Lastly, the Cache configuration allows integration with external cache systems (like Redis), enabling session persistence and performance optimization. Together, these settings ensure orchestrators operate securely, efficiently, and according to policy.

Publish a deployment

The Deployment Manager provides a means for you to publish and manage revisions of a deployment.

To publish a deployment click Publish to open the Deployment Manager.

Inspector Warnings

The inspector provides an early warning system to prevent you from sending configuration to an Orchestrator that it cannot handle. You should should resolve any warnings before publishing your deployment.

Simulation Settings

When deploying a Continuity Strategy, you can simulate identity service downtime. If you are not deploying a Continuity Strategy these settings have no effect.

Revisions

Here you can opt to publish a new revision or choose an earlier version and include a note. When you publish a new revision, the diff view shows a comparison between the currently active version and the new changes in the release.The green highlight indicates additions and the red highlight indicates removals from a deployment.

When selecting a previous revision, this will roll back the deployment to a previous state. It will not change any of the configuration states indicated in the console.