Stash is now known as Bitbucket Server.
See the

Unknown macro: {spacejump}

of this page, or visit the Bitbucket Server documentation home page.

Stash provides a simple way for user accounts and other systems to connect securely to Stash repositories, using SSH keys, in order to perform Git operations. You can:

  • add a personal key to a Stash user account to allow a developer to easily authenticate when performing read operations from his or her local machine. A Stash user can add any number of keys to their account. Read more at SSH user keys for personal use.
  • add an access key to a Stash project or repository to allow other systems, such as build servers like Atlassian's Bamboo, to authenticate for either read-only (pull, clone) or read-write (push, merge) operations, without the need to store user credentials. Read more at SSH access keys for system use.

Related pages:

Before you can use SSH keys to secure a connection with Stash the following must have already been done:

  • your Stash administrator must have already enabled SSH access in Stash.
  • you need an SSH key! See Creating SSH keys. Alternatively, you can use an existing key, if it isn't already being used as a repository or project access key in Stash.

Note that:

  • You can use the same SSH system access key for multiple repositories or projects.
  • A Stash user can add any number of keys to their account.
  • Keys used for personal user accounts can't be re-used as a project or repository access key, and keys used as a project or repository access key can't be re-used for user accounts.
  • Stash supports DSA and RSA2 key types – RSA1 is not supported. 

 

  • No labels
 

 

 

 

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.