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

Confluence Active Directory and public access

Alex Suslin

Hi all,

We're going to have one place for all our users for JIRA, Confluence and Google apps. As I know the downloaded version of JIRA and Confluence are not supported Google Apps integrations, so we have decided to use Active Directory as a main users storage.

As far as I know, if the JIRA or Confluence license for 100 users (and in AD we have more than 100 users), the license user counter will be applied to a number of users in groups (jira-users or confluence users). Am I right?

And the second, is it possible to have AD authentication for our internal users and still have public access for our customers to confluence (kinda Forms authentication for them)?

Thanks in advance and looking forward to hearing from someone :-)

Accepted answers

Colin Goudie

Sounds like you have mostly worked it out, but here goes

1. Your license count will be for those users with the 'use' permission. By default this will be the two groups as you mentioned but since you can modify which users/groups can have the use permission, just remember to take that into account. i.e. It isn't hardcoded to those group names

2. Yes, you can have an AD directory added for your internal users, and put the external users into the Internal JIRA/Confluence user directory

3. If you are really wanting authentication via Google Apps, we at AppFusions have a product for that, so just get in contact if you were keen to try that route

Cheers

All comments

Colin Goudie

Sounds like you have mostly worked it out, but here goes

2. Yes, you can have an AD directory added for your internal users, and put the external users into the Internal JIRA/Confluence user directory

3. If you are really wanting authentication via Google Apps, we at AppFusions have a product for that, so just get in contact if you were keen to try that route

Cheers

Andrew Frayling

Hi Alex,

For Confluence the number of users counted towards your license is actually the number of users that have the "Can Use" permission - http://confluence.atlassian.com/display/DOC/Global+Permissions+Overview - which is generally the users in the confluence-users group, but the total number of users in your install with "Can Use" will depend on your group/permission configuration. For JIRA it's the number of users that can log in, which is everyone in jira-users.

For public access to Confluence you can enable Anonymous Access - http://confluence.atlassian.com/display/DOC/Setting+up+Anonymous+Access - and structure your content so that some Spaces/Pages are viewable publicly, but there wouldn't be any authentication, the Spaces/pages you configure to be anonymous would be completely open. If you want some sort of authentication for your customers so that Confluence is not completely open then Confluence would need to know about those users and therefore they would count against your license.

You can also configure JIRA to allow anonymous access if you want - http://confluence.atlassian.com/display/JIRA/Allowing+users+to+create+issues+anonymously

Hope that helps?

Andrew.

Alex Suslin

Thanks for your comment, howerver if the option to connect all thr products with google apps will be the priority, we still may have an option to use JIRA CROWD.

And thank you for your answer, it helps.

Alex Suslin

Yes, I know about the licesing policy and the idea is that for example we have 150 confluence users (confluence licence will be 500 users) and like 100 customers (we will create logins for them manually). Company users will user AD authentication and customers should have access without AD account, however the anonymous users have to be disabled.

Welcome!

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

Quick Links

Find more posts tagged with

confluence

permission

user-management

ldap