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!
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.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot