Resolving Authentication Errors for Projects Using Git or Other Remote Providers

Article #: SCC1010F-B Product: Flare Version: All

Before You Begin

Complete Part 1 of Git / Source Control Authentication Errors before following the steps in this topic. Resetting the credential and configuration environment is required in every scenario.

For non-Flare Online repositories such as GitHub, Azure DevOps, Bitbucket, or a self-hosted Git server, authentication is handled by Git for Windows. As long as the binding was set up through Git for Windows, or Git for Windows is enabled in Flare, you will receive the modern Git for Windows authentication prompt, where you can enter a password, a personal access token (PAT), or complete a browser-based sign-in.

References: Binding a Project to Git, Importing a Project From Git

Re-Authenticate Through Git for Windows

  1. Confirm that Git for Windows is enabled in Flare. Select File > Options > Source Control and verify that the Git for Windows option is enabled.
  2. Select the Source Control ribbon and choose Push or Synchronize.

  3. When the Git for Windows credential prompt appears, complete the sign-in method required by your provider:

    • Password or PAT: Enter your user name and the password or token in the prompt.
    • Browser-based sign-in: Follow the prompt to authenticate in your default browser, then return to Flare.
  4. After successful authentication, Git Credential Manager stores the credentials in Windows Credential Manager, and you should not be prompted again.

Note: If your organization uses multi-factor authentication (MFA), password authentication may be rejected. Generate a personal access token from your Git provider and use it in place of your password. Confirm the token has not expired and has the correct repository permissions.

Import Project From Source Control

If authentication still fails, or if your project shows a large number of files pending commit, import a fresh copy of the project from source control. This is the only resolution for the pending-commit symptom. Delete or rename the existing local project folder first, then import to a clean destination.

  1. Select Source Control > Import Project, or from the Start Page select Import Project From Source Control.
  2. Choose Git as the provider.
  3. Enter your repository URL and complete the authentication prompt.
  4. Choose a destination folder and finish the wizard.
  5. Once imported, verify that you can push and pull without errors.

Note: If your project is dual-bound to Flare Online and Git, always import from Git so both bindings are preserved.

Still Need Help?

If the issue persists, contact MadCap Software Support and include your Flare version and build number, your Git provider, the exact error message and error number, and whether the project is single-bound or dual-bound.

Attribution:

Last updated:
September 8, 2026		 Author:
Ian Hinkle		 Contributions by: