I would like to enforce my team to use only Google SSO to login to bitbucket. Right now, if the account is created first, it can be login using both Google SSO and previous login credential. If the account is created with Google SSO at the beginning, it is working fine. Do I need to remove all the user account and recreate again to enforce Google SSO?
There is no way to force users to use Bitbucket in any specific way, including the way they choose to log in. Accounts are owned by their users and are not under the control of the teams they are a member of.
If a user signs up through Google, they can still set a password and log in with that the next time.
We need to be able to log in to our BitBucket Server using Google Accounts, similar to how JIRA Cloud hooks up to a google domain. I am sure many people would rejoice if you made this possible, NOT via a Crowd directory, and NOT via a JIRA directory!
Hi Erik and Elisa,
Thanks for the update. I was expecting Bitbucket would able to force with SSO setup but seems cannot able to have it. Is this because of we are using bitbucket-cloud service? If we are on Stach server, would this able to get it done?
As far as I understand, your need is to prevent users from having multiple credentials to access to the same account.
If you used Atlassian server versions (including Stash/Bitbucket server and Crowd), you could force your users to log onto your Atlassian products and Google Apps with their Crowd credentials only.
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs