Our users are not locally managed in Confluence, but rather in a central setting in an LDAP - can Space Privacy still be used?
Yes, the plugin also reaches LDAP users as long as it was configured in Confluence Administration.
However, it is absolutely necessary for local groups to be allowed, as space privacy creates groups for every extranet space. Users, that are assigned to the corresponding extranet space, are added to these groups.
We manage content permissions through the permissions for the confluence spaces in predefined groups. Consequently, content permissions remain unchanged even after the plugin is deactivated. Contrary to single permissions these predefined groups make sure that the extranet user administrator doesn’t have to be the space admin as well. In Confluence, only space admins can assign new permissions. With the admin role extranet user administrator we have created the possibility to give users, that aren’t or are not allowed to be space admins, administrative rights over the user administration of extranet spaces.
If a user is added to a extranet space, they won’t show up as a single person in the permission. Instead they are part of the group(s) that were created for this space by space privacy, e.g. extranet-SPACEKEY-consumer.
If the Plugin can’t use these extranet groups, the following error occurs:
This also applies, if the user administration isn’t done in Confluence, but in JIRA (or others) instead. You will find the option to allow local groups here as well.
If you have any questions about this, don’t hesitate to ask us. We would love to help you!
Using JIRA servers or Atlassian Crowd as a user directory
There’s no option “Read Only, with Local Groups” for JIRA Servers or Atlassian crowd. In this case the configuration consists of 2 steps. Firstly the option “Read/Write” has to be set for the user directory (JIRA server or Atlassian Crowd). Secondly the option “Read Only, with Local Groups” has to be configured in the tethered user directory.