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

IP Whitelisting for specific confluence space

Roger Wahl

Hi there,

we enabled the public links in our confluence cloud premium. One of the space admins has a new request. He wants to restrict the access via the public link to specific IP addresses.

If am not mistaken one can restrict the access via IP whitelisting. Now to my question. Is it possible to limit the access restriction only to a specific space (or pages) and not to the entire product?

I have found contradictory statements online. Therefore my question.

Best thanks in advance!

Roger

Accepted answers

Ollie Guan

Hi @Roger Wahl ,

Cloud: Confluence Cloud does not support IP whitelisting for specific spaces. IP whitelisting can be applied at the site level.

Data Center: You can configure IP whitelisting using reverse proxies or firewalls.

Vote for this Suggestion

https://jira.atlassian.com/browse/ACCESS-1040

Kristian Klima_gtcuat

HI @Roger Wahl and welcome to the community.

There are two levels of your issue.

Technical level - IP whitelisting etc.

You may want to review this and see if it applies to your use case.

https://support.atlassian.com/security-and-access-policies/docs/specify-ip-addresses-for-product-access/

I know of a case where a company is using Scroll Viewport app (by K15t) to restrict access from certain regions.

Also, if you have Atlas (Atlassian Access) and SSO, you may find a solution there.

Conceptual content level

You said that you enabled public links for individual pages. Perhaps you do have a use case to do that but it complicate things if you want to have a more granular control access over your public/customer facing content.

So I'd look into creating your docs strategy - what content you want to make available, to whom, and how to achieve that in a more manageable way.

For example, our documentation lives in a single private space (no public links, no anonymous access) and we use Scroll Documents, Variants and aforementioned Viewport to create two documentation site - Public and Internal. The internal site is behind our SSO)

The setup allows us to control which pages, or even sections of the pages, appear in which site.

Should we want to, we can create another site behind SSO that would be set up for our customers - so they could log in to that site (without Confluence seat) with their existing customer login.

Setups like that are easier to manage and support long term - especially compared to managing a plethora of individual public links and a selection of IP restrictions.

Hope this helps.

All comments

Ollie Guan

Hi @Roger Wahl ,

Cloud: Confluence Cloud does not support IP whitelisting for specific spaces. IP whitelisting can be applied at the site level.

Data Center: You can configure IP whitelisting using reverse proxies or firewalls.

Vote for this Suggestion

https://jira.atlassian.com/browse/ACCESS-1040

Kristian Klima_gtcuat

HI @Roger Wahl and welcome to the community.

There are two levels of your issue.

Technical level - IP whitelisting etc.

You may want to review this and see if it applies to your use case.

https://support.atlassian.com/security-and-access-policies/docs/specify-ip-addresses-for-product-access/

I know of a case where a company is using Scroll Viewport app (by K15t) to restrict access from certain regions.

Also, if you have Atlas (Atlassian Access) and SSO, you may find a solution there.

Conceptual content level

So I'd look into creating your docs strategy - what content you want to make available, to whom, and how to achieve that in a more manageable way.

The setup allows us to control which pages, or even sections of the pages, appear in which site.

Should we want to, we can create another site behind SSO that would be set up for our customers - so they could log in to that site (without Confluence seat) with their existing customer login.

Setups like that are easier to manage and support long term - especially compared to managing a plethora of individual public links and a selection of IP restrictions.

Hope this helps.

Roger Wahl

Thanks a lot for this plain and simple answer!

Kristian Klima_gtcuat

@Roger Wahl Point taken

Roger Wahl

Sorry I wasnt refering to your answer. The Atlassian documentation was very unspecific and in parts confusing.

Welcome!

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

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud