If you were using TaraVault Git on Spira versions 6.6.1 or earlier, when your instance was upgraded to Spira 6.7, the source code module was updated to use the brand new SCM features in Spira 6.7. These new features use a different method for connecting to Git and may need you to update the connection inside Spira.

You will know there is an issue if the Developing > Source Code or Developing > Commits pages remain blank and you get a recurring error in the Event Log that Spira cannot authenticate with TaraVault.


The solution is as follows:

  1. Login to Spira as the 'administrator' user.

  2. Open up the User Profile page for the 'administrator' user.

  3. Switch to the TaraVault tab.

  4. Put in a new password.

  5. Click Save
  6. The connect between Spira and TaraVault will be restored.