Opsera MOMentum: Innovating with Heart
RELEASE UPDATE - MAY 2025
SDLC
SCIM-Based User Provisioning & Role Management with Microsoft Azure
Opsera integrates seamlessly with Microsoft Azure Active Directory via System for Cross-domain Identity Management (SCIM), enabling enterprises to scale DevOps teams, manage contractor access, or adhere to strict compliance mandates.
With this capability, Opsera supports Azure AD user provisioning to automatically create, update, or delete user accounts in Opsera. This centralized management automates user setup and accurately syncs attributes like emails, group memberships, and roles.
Key Features include:
Automated onboarding/offboarding: Users gain or lose Opsera access instantly as they join/leave teams or change roles in Azure AD.
Role Consistency: Maintain uniform permissions across Azure and Opsera, reducing security gaps from outdated privileges.
Enterprise Compliance: Align with internal audits via detailed provisioning logs and safeguards like Prevent Accidental Deletion.
Note: For Opsera SCIM Credentials, the Tenant URL and API token can be retrieved under SCIM Settings Configuration in Opsera.
Seamless Android CI/CD Automation with Enterprise-Grade Security
Opsera delivers end-to-end automation for Android app builds, signing, and publishing, designed to accelerate delivery while prioritizing security and compliance. With this update, teams can:
Automate the creation of APK (debug/release) and AAB (Play Store-ready) artifacts directly from Pipeline, triggered seamlessly by Git pushes to main or feature branches.
Sensitive signing credentials, such as keystores and API keys, are securely stored in Opsera’s encrypted vault, and injected dynamically during pipeline runtime.
Failed unit tests, missing dependencies, or invalid keys trigger immediate pipeline halts, preventing flawed builds from advancing.
By eliminating manual steps, your teams can ship high quality Android apps faster and scale workflows confidently.
Cross-Account IAM Role Assumption via Automation Dummy Roles
Opsera has introduced a streamlined way to manage cross-account deployments in EBS. With this capability, teams can utilize automation dummy roles to assume deploy IAM roles without the need for manual entry of Amazon Resource Names (ARNs).
The EBS Deploy workflow enables cross-account IAM role assumption by retrieving these roles directly from Opsera’s tool registry. By enabling AWS accounts to register automation dummy roles, organizations can ensure a more efficient and error-free deployment process.
Note: As new roles are added or existing ones modified in the tool registry, these changes are reflected automatically in the deployment process, preventing outdated configurations.
Enhanced Dry Run Summary Report with Status Tracking
The Dry Run Summary Report now offers a comprehensive view of repository validation results. The capabilities includes:
A Status Column to indicate whether a repository passed (Success) or failed (Failed) validation during a dry run.
The summary report will now include failed repositories to ensure all issues are identified.
Salesforce
Enhanced Code Scan Visibility in Merge Sync Workflows
The Diff screen in the merge sync workflows (Salesforce to Git and Git to Git Merge Sync task), features real-time code scan vulnerability detection. Developers can see a bug icon next to vulnerable lines directly in their files while reviewing code changes. Clicking the icon opens a detailed panel displaying a list of all vulnerabilities associated with that specific line.
Error Title/Message and description
Line and Column Numbers for precise issue localization.
Category, Rule Name, Engine, and Severity to prioritize fixes.
Please note that the code scan must be enabled for the merge sync workflows, in order to view this vulnerability panel.
Enhanced Visibility for User-Modified Files in Merge Sync Workflows
This capability adds intuitive visual indicators to files modified manually during synchronization workflows. When a user edits or saves a file, a check mark icon appears next to its name.
Quickly trace manual interventions in collaborative workflows, simplifying compliance reviews and issue resolution. This eliminates confusion between automated sync actions and human-driven edits, reducing the risk of accidental overwrites.
Streamlined PR Validation Summary & Enhanced Debugging Links
This enhancement delivers:
Cleaner, more focused interface by eliminating visual clutter like redundant spacing and inconsistent formatting.
Instantly access error details directly from the summary screen. Any failed validation steps include direct links to their corresponding console logs or detailed reports.
Enhanced Progress Tracking for Salesforce Bulk Migration
Salesforce Bulk Migration Logs has been enhanced to deliver granular, real-time visibility into component retrieval and processing.
Now, status messages will include detailed progress updates at the individual component level. In addition, messages will pinpoint stalled or failed components, accelerating troubleshooting. This ensures teams stay informed throughout the migration lifecycle.
Platform
Introducing Audit Logs for Site Roles
The Audit Log Displayer is integrated into the detail views for Groups, Site Roles, and Users.This allows administrators to view audit logs directly within the context of a specific user, group, or role. This provides immediate visibility into actions like permission changes, membership updates, or role modifications.
Each audit log entry for an ownership transfer will include the previous owner, new owner, resource type, and timestamp, providing a clear record of access changes. This update focuses on logging only the modified ownership data.
Entitlements for User/Group Resource Limits
A new entitlement feature has been designed to limit the number of users and groups that an organization account can create.
Upon enabling this entitlement, organizations will have a predefined limit on the number of users and groups they can create. The entitlement will be configurable, allowing administrators to view current usage against their limits. When an organization attempts to create additional users or groups beyond their allocated limit, the system will deny the request and provide a clear error message indicating that the limit has been reached.
Note: By default, this entitlement will be in a disabled state. Organizations must explicitly enable it if they wish to impose these limitations.
Last updated