Error: Inauth due to password auto-population in automations - ConnectALL
search cancel

Error: Inauth due to password auto-population in automations - ConnectALL

book

Article ID: 445086

calendar_today

Updated On:

Products

ConnectAll SaaS ConnectALL ConnectAll On-Prem

Issue/Introduction

After upgrading to ValueOps ConnectALL 4.2.0, automations for JIRA Cloud connections may fail. This issue occurs when the user interface incorrectly auto-populates or overwrites API tokens with browser-saved credentials.

Symptoms:

  • Automations fail with an Inauth error.
  • The password or API token field is overwritten during automation modifications.
  • Clicking the magnifier next to a connection wipes the existing password field.

Steps to Reproduce:

  • Modify any automation on SaaS environment.
  • Just click the magnifier next to the JIRA connection, and it validates successfully. Without hitting re-configure or configure here. This re-fills my API token in the Password field.
  • Navigate  back to the automations page and reopened to modify that automation. Fields load fine from Rally and JIRA. 

Expected Results: 

  • Connection manager page should not wipe the  API password.

Actual Results:

  • Connection manager page has wiped  API password again.

Environment

  • ConnectALL Saas 
  • ConnectALL On Prem

Cause

Defect DE205153. The ConnectALL UI auto-populates the sync user and password fields with credentials saved in the browser (e.g., Chrome password manager), which overwrites the correct API tokens.

Resolution

Fixed in release 4.2.2 and higher.