Page tree
Skip to end of metadata
Go to start of metadata

Linchpin User Profiles - Documentation

Create a meaningful and up to date profile

See the documentation for your Release

Installation & Licensing

The Custom User Profile plugin is a type two add-on, please follow the installation instructions as given by Atlassian: Installation steps via Universal Plugin Manager

  1. Log into your Confluence instance as an administrator.
  2. Click the admin dropdown and choose Atlassian MarketplaceThe Find new add-ons screen loads.
  3. Locate Custom User Profile via search. The appropriate add-on version appears in the search results.
  4. Click Try free to begin a new trial or Buy now to purchase a license for Custom User ProfileYou'll be prompted to log into MyAtlassian if you're logged out. Custom User Profile begins to download.
  5. Enter your information and click Generate license when redirected to MyAtlassian.
  6. Click Apply licenseIf you're using an older version of UPM, you can copy and paste the license into your Confluence instance.

Compatibility

Plugin4.35.25.45.55.65.75.85.9
Release 1.14(error)(error)(error)(tick)(tick)(tick)(tick)(tick)
Release 1.13(error)(error)(error)(tick)(tick)(tick)(tick)(error)
Release 1.12(error)(error)(tick)(tick)(tick)(tick)(tick)(error)
Release 1.11(error)(error)(tick)(tick)(tick)(tick)(tick)(error)
Release 1.8 - 1.10(error)(error)(tick)(tick)(tick)(tick)(error)(error)
Release 1.4 - 1.7(error)(error)(tick)(tick)(tick)(error)(error)(error)
Release 1.3(error)(tick)(tick)(tick)(error)(error)(error)(error)
Release 1.2(error)(tick)(error)(error)(error)(error)(error)(error)
Release 1.1(tick)(error)(error)(error)(error)(error)(error)(error)

 

New in 1.14: Incremental LDAP Synchronization

Use an incremental LDAP synchronization of your user data to only import modified user data and benefit from a faster synchronization.

Workaround for newly added profile fields

 If you add new profile fields after you already activated the incremental sync, they won't be synchronized automatically. In this case simply clear the "Last LDAP sync date" field. This forces a full sync once, which will result in synchronizing all fields including the new ones.

Go to Data Sources in the administration panel and select the LDAP tab.

Enable the incremental synchronization if you want to reduce time and server load. The next run of the LDAP sync will use the date defined in the field to "Last LDAP sync date" to synchronize only users who have been modified from that date up to now. Every time the sync job runs, it will set this date and time new. So usually you don't have to change anything here, except for two cases:

  • you want to force a complete synchronization once: empty the field.
  • you want to synchronize all users' data that has changed since a specific date: enter that date and time. 

The plugin internally uses the timestamp format dd-MM-yyyy HH:mm:ss
So if you want to manually enter a date, you have to use this format, e.g. 23-05-2016 15:00:00.

Define the timestamp pattern of your LDAP resource

In order to make the synchronization work, the plugin needs the exact timestamp pattern your LDAP resource uses for storing the "last modified date" information. Please enter the pattern in the second input field.
Information for different timestamp patterns can be found here. 

Examples:
yyyyMMddHHmmss.Z (known to work for a lot of AD installations)
yyyyMMddHHmmssZ (known to work for a lot of OpenLDAP installations)

(warning) Please make sure that all connected LDAP systems use the same timestamp pattern, otherwise no data will be synchronized.

 

Data sources

 

You can add an alternative LDAP and an XML import (p.e. from a SAP Export) to fill your users' profiles automatically.

 

 

Restricted categories

 

You can now restrict profile field categories to prevent users from seeing fields they don't need. 

By choosing group restrictions, all profile fields within this category are only viewable / editable for users within the configured groups. 
Users from other groups will not see these field in their profile. By default no groups are configured, so every user has the profile fields from this category.

(warning) This is not a security restriction, it is meant to reduce overhead for users! If a user has set a field, which is restricted later, the value can still be found in the search.

Theo Schröder ist in the "confluence-administrators" group, so he can see and edit all fields inside the "Admin only knowledge" category.

Kathrin Holmes is not in this group, therefore she can't see this field in her profile.

 


Profile-Editor

Custom landing spaces

 

Set up custom landing pages for users based on their user profiles. After logging in, users are redirected to a customized space, e.g., the team space for a certain location and department. 

 

 

Org Charts

 

You can now define which field of the type "User select (autocomplete)" holds the superior/subordinate connection of one user to another.

 

 

 

 

Import user data from your LDAP

 

To update the LDAP data in the user profiles regularily a scheduled Confluence job ("Bulk profile update (LDAP sync)") will try to connect to the configured LDAP and update the user profiles.

You can configure the execution time of that job as desired or even manually start the import there.

Known Issues

"Profile Updated" by Anonymous due to Confluence Synchronization

When Confluence synchronizes against any external user management, all of the newly created and updated users will be displayed under the "All Updates" section of "Recently Updated" macro in Confluence dashboard.

Considering the amount of users Confluence will create or update from the synchronization, it would be better to be excluded from "All Updates" section. Or at least, Confluence should provide the option to exclude these updates.

From Confluence 5.5 and later you can add the following argument in your JVM options to prevent updates to user information appearing in the dashboard https://jira.atlassian.com/browse/CONF-32081
   

-Dconfluence.dashboard.recentlyupdate.filtertypes=page,comment,blogpost,attachment,spacedesc,personalspacedesc,status
  

Parentheses in filters are treated wrong

Since we have introduced complex filters for your custom landing pages, parentheses in filters are treated as logical characters. So your filter might be broken if you try to filter by attributes containing parentheses.
A workaround would be using the wildcard '?' instead of a parenthesis.

Problems with uploading profile pictures using Internet Explorer

Im some server configurations, a problem can occur when uploading profile pictures using the Internet Explorer. This problem leads to a page with the text "Loading...", and the user is unable to resize the picture. If this happens, the following snippet can be added to the Apache configuration, which should solve the issue (example for .png-files):

<LocationMatch ".*\.png$">
ForceType image/png
Header set Content-Disposition inline
Header set Content-Type image/png;charset=UTF-8
</LocationMatch>

 

 


 

  • No labels