nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

You are currently connecting with your team account. This is no longer supported, so please connect

Kevin Shu

Hi,

I am using SSH Keys set on the team account to automate some operations related to my repositories (checkout, build, test, merge and push)

The server is emitting the following warnings :

remote: Warning!
remote: You are currently connecting with your team account.
remote: This is no longer supported, so please connect using your user account.

How am I supposed to update my process? The recommended way of providing automation seems to be using SSH Access keys, but these only allow Read-Only access, no write access.

Thanks

Accepted answers

All comments

Ana Retamal

Hi Kevin! You can not manage a repository using a team account anymore. Team administration changed and you can no longer use an email address to access a team or manage repositories using a team account. Now, team members use their individual Bitbucket accounts to access the team and commit changes. This was announced at Team account changes. You'll need to automate those operations using your individual Bitbucket account, given that your Bitbucket account has access to those repos.

Hope this helps!

Ana

Kevin Shu

Thanks Ana for your reply. I did see the page you mention but I was hoping there would be another way.

I also saw that Bitbucket Server allows SSH Keys with read-write access.

https://confluence.atlassian.com/bitbucketserver/ssh-access-keys-for-system-use-776639781.html

Is this something that is planned to be implemented in Bitbucket Cloud?

Adam Rocska

@Ana Retamal : What are we expected to do on our Continuous Integration solutions? It is quite irrational to use a specific software engineer's bitbucket account to have the CI server push versioning changes to Bitbucket. We have to register a standalone brand new Atlassian account for our bots?

Thanks in advance.

Ana Retamal

Hi @Adam Rocska, afaik you'll need to use someone's account or create a dedicated account to push the changes. I've tried finding some feature request for that, but to no avail. Feel free to submit yours in our Public Issue tracker.

Regards,

Ana

slmt

Totally agree with @Adam Rocska and @[deleted]. Registering a bot as a regular user is just... wrong.

My use case is Bitbucket Pipelines. I have three custom pipelines corresponding to the three numbers in semver (major, minor, patch) which need to push a tag and changes to master and develop. The problem is that git in Pipelines can't push to the remote, so I generated a team-level SSH key and set that as the SSH key in Pipelines. I'd be happy to do away with the team-level SSH if Pipelines can be enhanced to allow pushing back to remote.

wkunker

I'm also in the "I don't understand this" bucket. What if I want to use my account for multiple organizations? How can I add an SSH key with r/w permissions without exposing it to multiple organizations?

Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

team-account