Modifying the oauth secret after a failed attempt does not work until a connector service restart

XMLWordPrintable

      Issue Summary

      Modifying the oauth secret after a failed authorization attempt does not work until a connector service restart is performed. So, when we modify a bad secret and then try to re-authorize, the updated secret is not being picked up by the service unless we restart the ADO connector.

      Steps to Reproduce

      • Change the authentication method to Oauth in the ADO connector
      • Input an incorrect secret and perform authorization
      • Once failed, input the correct secret and then try re-authorizing
      • Notice that the sync does not work from JA to ADO
      • Perform a connector restart
      • Notice that the correct token is getting picked up and the sync is working fine

      Expected Results

      Modifying oauth secret after a failed authorization attempt should be picked up by the service successfully without a connector restart.

      Actual Results

      Modifying the oauth secret after a failed authorization attempt does not work until a connector service restart is performed.

      Workaround

      Restart the ADO connector service as a workaround for the new secret to be picked up by the service. That will help sync the work items from JA to ADO.

              Assignee:
              Yannick Genin
              Reporter:
              Arathi M S
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: