Troubleshoot

This page shows you how to resolve issues with Secure Source Manager.

Error message when creating a repository

The following error appears when you try to create a repository:

There was an error while loading /repo/create. Try refreshing the page.

This issue occurs when:

  • The Secure Source Manager API isn't enabled in your project.
  • You don't have the Repo Admin role on your project or permissions to create repositories in the Secure Source Manager instance.

To resolve this issue:

  • Enable the Secure Source Manager API in your project.
  • Ask your administrator to grant you the following roles:
    • Repo Admin (roles/securesourcemanager.repoAdmin) role on your project.
    • Instance Accessor (roles/securesourcemanager.instanceAccessor) on the Secure Source Manager instance.
    • Instance Repository Creator (roles/securesourcemanager.instanceRepositoryCreator) on the Secure Source Manager instance.

See Access control with IAM for more details.

Error message when cloning a repository on a Mac

The following error appears when you try to clone a repository:

git: 'credential-gcloud.sh' is not a git command.  See 'git --help'.
fatal: Authentication failed for [repo-url]

This issue occurs when:

  • gcloud CLI is installed using Homebrew or other non-standard installation.
  • git-credential-gcloud.sh is not added to your PATH.

To resolve this issue:

  • Run source $HOMEBREW_PREFIX/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/path.zsh.inc
  • Check that git-credential-gcloud.sh is in your path by running the following command:

    which git-credential-gcloud.sh
    

Git HTTPS requests fail with permission denied or unauthorized error

When Git commands are attempted over HTTPS, a permission denied or unauthorized error message is given.

This issue occurs when one of the following occurs:

  • The global Git config file is missing the Secure Source Manager authentication helper.
  • Git's built-in credential store is being used instead of calling the Secure Source Manager authentication helper to get a fresh credential.
  • A system credential helper is being used instead of calling the Secure Source Manager authentication helper to get a fresh credential.

To resolve this issue:

  1. Run the following command to determine the contents of your global Git config.

    git config --list | grep credential
    
  2. If you see any line similar to *credential*.helper=store on macOS, or credential.helper = manager on Windows OS, then remove those lines, and then re-authenticate using glcoud auth login before trying the Git command again.

  3. If the response doesn't include credential.https://*.*.sourcemanager.dev.helper=gcloud.sh, then add the Secure Source Manager authentication helper to your global Git config:

    1. To add the Secure Source Manager authentication helper to your global Git config, run the following command:

       git config --global credential.'https://*.*.sourcemanager.dev'.helper gcloud.sh
      
    2. Validate that the authentication helper line is added to your global Git config by running the following command:

       git config --list | grep credential
      

      The output should include credential.https://*.*.sourcemanager.dev.helper=gcloud.sh.

    3. Authenticate by running gcloud auth login.

    4. Run a Git command to test the authentication.

Project not showing up in web interface product selector

When using the Secure Source Manager web interface product selector, your project doesn't appear.

This issue occurs when you have multiple login credentials for Secure Source Manager.

To resolve this issue:

  • Clear your cookies by appending the following to your Secure Source Manager instance URL: /_oauth/consent

    For example, if your instance URL is https://my-instance-098765432123.us-central1.sourcemanager.dev/, enter https://my-instance-098765432123.us-central1.sourcemanager.dev/_oauth/consent into your browser address bar and then log in with the correct credentials.