Release Updates 02/21/2025

Platform & SDLC

Capability to Perform Vault Selection during Tool Registration Process

Opsera gives you powerful control over how your tool credentials are secured. Here's how it works:

• Centralized Control: Site administrators can choose a default vault (between HashiCorp and Thycotic) for storing all tool credentials, ensuring consistent security practices across your organization.

• Enhanced Security: For even stricter environments, site administrators can lock in the default vault selection. This prevents anyone from changing it when registering new tools, minimizing the risk of accidental misconfigurations or security gaps.

• Flexibility for Users: Even with these safeguards, users still have choices. When registering a tool, they can specify the vault they prefer (if allowed by the site administrator) and even choose a specific secret name within that vault for optimal organization and management.

This approach combines centralized security management with user flexibility, allowing organizations to meet their specific compliance needs while streamlining the tool registration.

Capability to Capture IAM Roles during AWS Tool Registration Process

Opsera's improved AWS tool registry integration now provides a more complete and streamlined way to manage Identity and Access Management (IAM) roles across your AWS accounts. This is especially valuable for organizations working with multiple roles and accounts, as it simplifies the process of capturing and organizing them. With this enhancement, you can precisely define which IAM roles your AWS credentials can access, eliminating manual errors and ensuring accuracy. Additionally, Opsera supports cross-account IAM roles, including those inherited from parent accounts, which is essential for organizations with complex AWS structures. This gives administrators a deep understanding of permissions and access controls across their AWS environments.

Secrets Capture in PR Validation Webhook Registration

Opsera now offers a more secure way to handle webhook registrations for GitHub repositories. When setting up a webhook for pull request validation, you can securely capture and store secrets within a vault. This adds an extra layer of protection by ensuring that only legitimate webhook deliveries from GitHub, matching the registered secrets, are processed by Opsera. This feature streamlines secret management and strengthens the security of your webhook integrations, preventing unauthorized access and potential malicious activity.

Capability to Downloading Detailed Reports and Displaying Repository Size for Dry Run Migrations

Users have the capability to download detailed reports for dry runs, similar to an actual SCM migration, along with the addition of a new column displaying repository sizes. This support offers users detailed insights into repository size, which is crucial for decision-making and planning, and aligns the dry run reporting experience more closely with that of actual SCM migrations.

Salesforce

Capability to Disable Lock Mechanisms for Tasks and Pipelines Wizards

Organizations can customize the lock mechanism for their Salesforce Pipeline and Task workflows by choosing to enable or disable lock mechanisms. Enable locks to prevent simultaneous access to certain tasks or resources, maintaining data integrity and preventing conflicts during execution. Whereas, disabling the lock screen minimizes clicks required to execute tasks, enhancing productivity and user experience.

Additionally, the option to disable the “auto assign lock if available” feature provides greater flexibility. Without this feature enabled, Opsera will not automatically create a lock when a task or pipeline is initiated without an active lock. This capability is particularly useful for organizations where developers manage multiple tasks simultaneously, allowing for quicker access and execution of workflows.