Change notice for Secret wallet and execution of Global parameters
Secrets wallet will be deprecated and replaced by Global parameters as the way to manage sensitive values in Usage Engine Cloud Edition. As part of the deprecation, you must move your secrets to Global parameters.
Global parameters are the single mechanism for managing both configuration and sensitive values going forward. This approach creates a simpler and more predictable way to handle configuration across your streams.
We have prepared the following information on what you need to know:
Why Secrets wallet is being phased out
Secrets wallet was designed for earlier use cases and has several limitations that become more challenging as solutions grow:
Secrets are customized per function with limited reuse. Each function configures its own secret, which reduces reuse across streams and functions.
Each function can use only one secret type from the Secrets wallet. This limits flexibility when a function needs more than one secret type.
Secrets do not follow a standardized structure or schema. This makes automation and consistent management harder.
Global parameters addresses these limitations and gives you a stronger foundation for security, reuse, and future capabilities. The goal is to make your daily work with configuration easier, more predictable, and more robust over time.
Benefits of this change
By replacing Secrets wallet with Global parameters, you gain several practical benefits in your day‑to‑day work.
Unified configuration model - A single concept for both non‑sensitive and sensitive values. This makes configurations easier to understand, document, and maintain.
Better reuse and consistency - Multiple functions and streams can reference the same Global parameter. This reduces duplication and configuration drift when configuration changes over time.
Stronger security posture - Sensitive values are handled through parameter references instead of direct entry into functions. This reduces the risk of accidental exposure and makes access control easier to manage.
Future compatibility - New capabilities and connectors will be built to work with Global parameters, ensuring your implementations remain supported as Usage Engine Cloud Edition evolves.
What this change means for you
This change is important for the stability and continuity of your solutions. If you do not move your secrets to Global parameters before the deprecation of Secrets wallets, any stream or function that still depends on the Secrets wallet will fail when it tries to access those secrets. To ensure a smooth process, there will be a migration window. For more on the dedicated migration window, see Change notice for Secret wallet and execution of Global parameters | When will this change happen.
Examples of password-like fields that are moved to Global parameters include S3 connectors, HTTP Client, and any other function that uses tokens, passwords, or API keys in its configuration, as these functions will have changes to password-like fields to support only parameter reference.
Since the Secrets wallet will no longer be accessible, it is strongly recommended that you export your streams before migrating to Global parameters. This gives you a safe backup of your current configuration and a clear reference point during the transition.
The intention of this change is not to disrupt your existing work, but to provide you with a clearer and safer way to manage configurations. You can use the migration window to plan, test, and adjust at a pace that fits your environment.
When will this change happen
There is a dedicated migration window to give you time to plan and adapt:
Migration window: Monday, the 4th of May 2026 to Wednesday, the 4th of November 2026
After Wednesday, the 4th of November 2026: The Secrets wallet feature will be fully deprecated and no longer available
During the migration window, you can still run your existing solutions while you migrate secrets and update configurations at your own pace.
After Wednesday, the 4th of November 2026, the Secrets wallet and all secrets stored in it will be permanently removed. At that point, any remaining dependencies on the Secrets wallet will cause errors at runtime.
What to do during the migration window
During the migration window, you must perform the following in order:
Recreate existing secrets in Global parameters - For each secret currently stored in Secrets wallet, create a corresponding Global parameter with a clear and traceable name.
Update functions and streams to use Global parameter references - After the migration window, direct credential fields that currently mask values, such as password fields, are updated to accept only parameter references. During the migration window, these fields continue to work as they do now and still mask values. If you do not update these configurations, there is a risk that passwords will be exposed when the fields are updated after migration. For every function in the affected functions list (see list below) that uses Secrets wallet or direct credentials, change the configuration to reference global parameters instead.
Stop creation of new secrets in Secrets wallet - Creation of new secrets in Secrets wallet is no longer supported. All new credentials must be created directly as Global parameters.
Migration guide
You can use this step‑by‑step guide to plan and carry out your migration: Migrating Secret wallets to Global parameters.
Support and feedback
Let us know how you like these improvements! Please share your feedback by using the Give feedback button in Usage Engine Cloud Edition. Your input helps shape how Global parameters and related features evolve in future releases.
If you have questions or need clarification, please do not hesitate to reach out to us through our Digitalroute Self-Service portal. We are here to support you throughout this transition.