On this page

What are dark features?

The dark features overview page is not reachable via the administration navigation. To open it, enter this link behind your Confluence's URL:

/admin/plugins/extranet/config/darkfeatures.action

Participant group

In version 3.3.0 of Space Privacy, we removed the extranet participant group. This group was very rarely used and removing it helped us boost the performance of Space Privacy.

If for some reasons you should need access to this group again, please activate the dark feature.

Doing this will activate participant groups again, as if version 3.3.0 wasn't installed (in regard to this feature).

Max Result Filter

Extends the number of max result parameter for user searches

As Confluence does not provide functions to restrict users, the mentions autocomplete is not filtered in any way and limits the search results to 10 by default.

With Space Privacy, it may happen that the first 10 search results are hidden users and the result is therefore empty.

By enabling this feature, the search results are extended to 50. We faced some problems on some instances, which lead to problems with mentions and user assignment. For more details, see the User and Group autocomplete returns "404 - Not found" section.

Skip Postgres Workaround

Deactivates deallocation for PostgreSQL prepared statements

Should an upgrade of the plugin fail and produce a log like this...

Caused by: org.postgresql.util.PSQLException: ERROR: cached plan must not change result type

...you might be using a PSQL database with a certain bug which can be circumvented with a workaround of enabling or disabling this dark feature.

After executing the request you can try to install or upgrade the plugin again and administration screens should be accessible.

Show Managed Groups

Make manage group available in group autocomplete (e.g. share page)

Managed groups are needed to provide extranet users the required content permissions and should only be used by Space Privacy. This is why they are hidden in autocompletes like sharing a page or setting restrictions.

If you need these groups to be available in such cases, you may turn this feature on.

Detailed Index State

Enables an endpoint for detailed index state information

If you got problems with indexing users in an extranet space you can activate the feature to get more information about the index state.

curl -u <username>:<password> "<baseurl>/rest/extranet/1.0/index-state/{spaceKey}/detailedIndexState"

This will return you a list of inactiveUsersInIndex and usersExistingInExtranetButNotInIndex. With this information you can identify which users are not indexing.

Troubleshooting

User and Group autocomplete returns "404 - Not found"

If you notice that user and group autocomplete (for example @-mentions, adding restrictions, sharing pages) does not work, this might be your problem.

This problem may occur in

• @-mentions;
• page shares;
• adding page restrictions;
• assigning new users / groups to an extranet.

To troubleshoot, please check the steps listed below.

1. Check the HTTP state

1. Open the developer console in your browser.
2. Switch to the "network" tab (page reload needed).
3. Open the user or group picker.
4. Check for a call which returns a 404 (should be a url like this: /rest/prototype/1/search.json?...).

2. Disable the max filter module

1. Open the Plugin Manager (/plugins/servlet/upm), find the Space Privacy plugin in the list and unfold it.
2. Open modules.
3. Disable the following modules:
   1. Max Results Servlet Filter (max-results-filter);
   2. Max Results Servlet Filter (max-results-filter-general).
4. Check the page from 1.1 again and see if the autocomplete works.

3. Server problem - quick test

If these tests solved your issue, then theres a problem with your server settings.

Your Confluence instance is not allowed to send HTTP requests to itself. This can have many reasons - please contact your server administrator for a solution.

You may also check this by using curl from the server your instance is running.

curl -u <username>:<password> "<baseurl>/rest/prototype/1/search/user.json?query=<existinguser>&max-results=10"

Replace <username>, <password>, <baseurl> and <existinguser> with real values.

This request should return a valid answer (a json object).