Check out the latest enhancements to Okta with OIDC!

**Multi-account sync**

Following the successful implementation of just-in-time provisioning support for Okta, we are taking it a step further by introducing multi-account sync for OIDC-Okta. This feature enables you to synchronize multiple Codefresh accounts in Okta simultaneously in Codefresh, ensuring a seamless SSO setup for enterprise customers.

With multi-account sync, you can easily select additional Codefresh accounts to sync with your Okta OIDC account in Codefresh. Codefresh validates admin privileges and access for each of the selected accounts, guaranteeing secure and reliable authentication.

You have the flexibility to sync users in multiple ways: through the UI's`Auto-group sync`, performing on-demand synchronization through the CLI, or integrating sync into a Codefresh pipeline using the CLI synchronize command.

**Delete users removed during sync**

We added an option to further streamline Okta SSO account and user management in Codefresh. You can now can easily remove individual users who are deactivated in Okta, not only from the current account but from additional accounts you have defined in your current account.

The Users list is updated, keeping both the Teams and Users lists always organized.

* Auto-sync option not available for Azure SSO (CR-18200)

* For an ECR integration, clicking**Test Connection** or**Commit** results in progress animations persisting instead of creating the integration.(CR-19124)

* Auto-sync option not available for Azure SSO.

* For an ECR integration, clicking**Test Connection** or**Commit** results in progress animations persisting instead of creating the integration.

* Invalid chart error on trying to access Codefresh Helm repository.

* Builds terminate unexpectedly without clear errors or from prolonged inactivity.

* DIND with service containers ignore IRSA account (IAM Roles for Service Accounts) set for hybrid runtime.

* Commit message passed through the system variable`CF_COMMIT_MESSAGE` is truncated and does not include the full content.

* Delay in start times for child pipelines triggered by parent pipelinethat includes a large set of`codefresh-run` steps set to run in parallel.

* Delay in start times for child pipelines triggered by parent pipelineincluding a large set of`codefresh-run` steps set to run in parallel.

* In Pipelines page, the context-menu for the last pipeline in the list does not display all available actions.

* Builds terminated because of pipeline policy leave running`dind` pods on runtime cluster.(CR-11485)

* In Pipelines Dashboard, for a renamed pipeline, the Pipeline filter displays the original name instead of the new name.(CR-18929)

* Builds terminated because of pipeline policy leave running`dind` pods on runtime cluster.

* In Pipelinesdashboard (HomeDashboard), for a renamed pipeline, the Pipeline filter displays the original name instead of the new name.

***Save** button remains disabled when modifying fields for an existing Git Source.

* Applications show**Unknown** status in Codefresh, while they are**Healthy** in the Argo CD UI.(CR-19442)

*Committing toan application in the same repository as another application, terminates the on-going rollout for the first application.

* Applications show**Unknown** status in Codefresh, while they are**Healthy** in the Argo CD UI.

*Commits toa second application in the same repository as another application, terminates the on-going rollout for the first application.

* (On-premises) Unable to create Git Sources both from the Codefesh CLI and UI with Bitbucket Server.

* (On-premises) For Azure, auto-sync operations removes groups that were previously synced.