Introduction

Bitbucket is a prominent source code repository hosting service, particularly for projects using either the Mercurial (since deprecated) or Git version control systems. When users sign up for Bitbucket using their Google accounts, it brings both convenience and new considerations into play regarding the management of Git credentials. This article explores the nuances of handling Git credentials in Bitbucket when signing up with a Google account, highlighting key technical details and offering practical examples.

Authentication Overview

When users sign up for Bitbucket via Google, Bitbucket associates the user account with their Google credentials. This means that the authentication process is primarily OAuth-based rather than relying on traditional username and password methods. However, for Git operations via the command line or for certain integrations, you may still require Git-specific credentials like an SSH key or an app password.

Types of Credentials

Here are the key credential types when working with Bitbucket after signing up with Google:

• OAuth Tokens: Automatically managed and renewed for browser sessions. If you are using Bitbucket within a browser session, OAuth tokens authorize your access.
• App Passwords: Used for accessing Bitbucket resources via command line or third-party applications. After signing up with Google, app passwords may be necessary for non-UI interactions.
• SSH Keys: Recommended for secure, key-based authentication seamlessly integrated with Git operations.

Setting up App Passwords

App passwords are essential for workflows involving Git operation on the command line or integration with CI/CD systems. Here’s how to create an app password:

1. Go to your Bitbucket account settings.
2. Select App passwords under Access management.
3. Create a new app password with relevant permissions for code read/write.
4. Use this app password in place of your account password when performing Git operations.

For example, you can use this app password for cloning repositories:

• Go to SSH keys under Access management.
• Click Add Key and paste your public key.