How to overcome the issue that DevOps Integrations application saving credentials in an unencrypted way (clear text)DescriptionSteps to replicate the issue: 1. Install the prerequisite plugins based on Install DevOps IntegrationsInstall DevOps 2. Setup the CreateDevOpsTool record based on Connect DevOps to Azure DevOps tools 3. Create new record of DevOps tools. 4. Open the Credentials record, show XML, password is plaintext. Cause of the issue: The DevOps app uses Connection and Credential Aliases to store user names and passwords for external tool integrations. When the standard "Create DevOps Tool" form is used to connect to a new tool using basic authentication, the password will be stored in plain text in the credential record. This is the case for any DevOps tool connection that uses Basic Authentication. The Dev team has confirmed this is a Problem (PRB1528310) and will be fixed in 'DevOps Integrations 1.33' plugin: DevOps Integrations In the meantime, there is a workaround available as below. Release or EnvironmentAny release using pre-version 1.33 'DevOps Integrations' plugin.InstructionsWorkaround: The password can be encrypted by editing and saving the credential record: Navigate to the tool record in the DevOps Tools list.In the "Tool Connections" related list, click on the credential link.Set a new password in the password field and click Update to save the change. After these steps, the credential password will be correctly encrypted. Note: It is necessary to make a change to the password rather than re-entering the existing one. If you wish to retain the current password, first change the password and save it, then re-enter the original password and save it again. These steps must be followed for each tool connection with basic authentication credentials associated with it.