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

[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

[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.

[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

[Deleted user]

I whole-heartedly agree with @Adam Rocska.  What your suggesting we do, using an individual's SSH key for what's effectively a service account, is atrociously bad practice.

If the only way to do it is to create a new dedicated account then I guess that's what we'll have to do, but that's really chumpy. Why the change?

[Kevin Shu]

Following @Ana Retamal's suggestion, I created a feature request on the public issue tracker

https://bitbucket.org/site/master/issues/15600/ability-to-use-service-account-on

[pdenti]

Whoa, I have been fighting with that as well. this is probably the worse specification in the Atlassian history.

Actually using the personal account for automated flows is the worst possible idea, just over the bad.

I think the reason behind this is just commercial, it cannot be anything else, not technical of course because it is against any right way to do things.

Access keys are read-only, team keys are basically removed as well.

It looks they want "regular users" (that is paid users) even for automated processes.

Too bad.

[wkunker]

This is the kind of thing that drove people away from GH. Wonder what's next now that BB is moving in that direction.

[Marko Kirves]

I'm seeing this error when following steps documented in Push back to your repository support document.

Trying to understand if this is going to break at some point or not or if the message I'm seeing is just a false positive error.

[Petr Horcicka]

if Atlassian removes the capability to push changes into a repository using a service account from a CI/CD pipeline I will recommend leaving the Atlassian platform to all my customers!

Just to make crystal clear who is paying for what...

[James Francis]

I'm in the same situation as Marko Kirves above - I'm trying to set up a push in a pipeline and getting that error. Pushing using a "user-based" account doesn't seem right, so would I need to set up a dedicated "Bot" user account for this and use OAUTH? The documentation states that "pushing back using http will work seamlessly", but messing around with OAUTH tokens is definitely not seamless!

[Marko Kirves]

I've raised my issue in Issue #18009:

https://bitbucket.org/site/master/issues/18009/push-back-to-your-repository-team-account

Based on the answer from @Graham Gatus this seems to be an issue with a false positive warning in my use case.

I'm still able to push tags back to my repository without setting up service accounts or additional authentication.

[James Francis]

Thanks Marko, glad to know I've not done it completely wrong and it's only a false positive.