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; } } }

Restricting access of external projects and users

David Co

I'm trying to restrict access of external bit bucket accounts from within my network while also allowing access to my own company's repos. Essentially I'd like to prevent external users logging in to my network. I'm currently using bitbucket cloud and trying to restrict this with a squid proxy without any luck.

Does anyone know how to solve this ?

Accepted answers

All comments

Ben

Hey David,

With a premium subscription to Bitbucket Cloud, you can control access to your private content by allow listing only certain IP addresses, there is further information on this located here:
https://support.atlassian.com/bitbucket-cloud/docs/control-access-to-your-private-content/

Cheers!

- Ben (Bitbucket Cloud)

David Co

Hi Ben, we do have a premium subscription but that is not the issue.
I'm trying to prevent our intellectual property. ie. someone signing into their personal account and then checking in all my company's code

Ben

Hey David,

If you are trying to prevent access to repositories - as long as those repositories are private, only authenticated users which belong to that workspace with the necessary permissions will be able to access/clone etc those repositories.
For instance, if a user logged into their personal account, and that account is not present on a list of users in the workspace - the content will not be accessible to them (for instance in a browser).
Similarly, if they try to clone the repository - they will receive an authentication error as the account being used to authenticate with the workspace is not on the list of authorized users.

Cheers.

- Ben (Bitbucket Cloud)

David Co

Hi Ben,

Thanks for replying, but I think I haven't explained this well enough.
Let's say we have an employee name EmployeeA.

EmployeeA has access to the company workspace and is authenticated.

EmployeeA ALSO has a private PERSONAL bitbucket account.

The scenario I want to prevent is EmployeeA logging into to his PERSONAL bitbucket, copying all the files from the company workspace and pushing it to his own PERSONAL repository - effectively taking a copy of the company's code

Cheers

Welcome!

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

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud