Linchpin User Profiles - Documentation

Create a meaningful and up to date profile

See the documentation for your Release

LDAP Configuration

Custom User Profile uses the directory services already configured in your Confluence. All profile fields used by Confluence will be migrated to Custom User Profile. Since the migration of the user data can take some time, you need to trigger it manually in the Profile Field Configuration section.

If you are using version 1.3 or earlier of this plugin, please refer to the LDAP configuration.

If you use Crowd ...

Custom User Profile is not able to get user data via Crowd. For using LDAP data it is neccessary to configure a direct connection to your LDAP system. You can do this by adding a new LDAP connection in the according configuration dialog (see e.g. https://confluence.atlassian.com/display/DOC/Configuring+User+Directories) and sort this at the end. Confluence itself will then use Crowd, Custom User Profile will use the next supported directory in the line.

Profile Field Configuration

Located behind the link 'Profile Editor' on the confluence administration screen.

Profile category and field list

You can create and manage profile categories to group fields. Profile fields can be assigned to a group.

Special fields

  • A user's display name
  • A user's profile picture: URL, LDAP attribute or Confluence

Display Name

As a confluence administrator you can flexibly define the look of your users' full names.
Go to the CUP Profile Editor on the administration screen and switch to the special fields tab. Insert your desired values into the text box labelled 'full name' to set up a user's displayed full name. Use any of your previously created LDAP fields in curly brackets as variables.
For example: {xup.academictitle-1} {xup.firstname-2} {xup.lastname-3}

Profile Picture: URL, LDAP attribute or Confluence

The Custom User Profile plugin can download profile pictures directly from your LDAP directory, from a custom URL or uploaded by the user itself.
As a confluence administrator go to the 'Profile Editor' screen in the administration area and switch to the special fields tab. Use the radio buttons to select if you want to use profile images from Confluence, an URL, or a LDAP attribute. If you select URL you can enter an URL pointing to the users' profile picture in the text field below. Use any of your previously created LDAP fields in curly brackets as variables (Example: http://mypictures.net/{xup.anyfield-1}/user/{xup-userid-2}.png). If you select the LDAP option,  enter an LDAP attribute for the users' profile picture (You can use JPEG- or PNG-Pictures) in the text box below (Example: jpegPhoto). You can also set the maximum size of the profile picture, this can be necessary for privacy reasons or disk space issues. The Images will be automatically re-sized on upload.

Profile field types

Text input

A text input is a single line text which a user can fill at will.

Select

For a select you can define options for the user to choose from. All possible options must be configured. The user can only select exactly one value from option list.

Multi-Select

A multi-select is basically like a select except that a user can choose any number of options. See example screenshot of a multi-select configuration.

Retrieved from LDAP

If you set up an LDAP field, add the LDAP attribute name which should be retrieved for each profile update.

Date input

A date field allows the user to select and store a date in his or her profile.

User select (autocomplete)

A user select field displays an input field which will autocomplete user names. It can store only one user name and will display a link to the users profile.

Language select

A language select displays a list of languages. Users can select multiple entries.

Scheduled profile update job

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.

Synchronized Confluence profile fields

Since release 1.4 the default Confluence profile fields are migrated into Custom User Profile fields. Starting with release 1.6, all changes to these migrated fields will be kept in sync with the default Confluence fields. So if you need to disable the Custom User Profile, the Confluence profile fields will still be up to date.

Configure a custom landing page (space)

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.

Add a help text for profile edit

Provide information for your users when they edit their profile. You can give them hints why certain fields (LDAP) cannot be edited by the user, or add a support email address.

 

  • No labels

This content was last updated on 02/03/2015.

This content hasn't been updated in a while. That doesn't have to be a problem. Some of our pages live for years without becoming obsolete. Please click this link if you want us to update this page. Old content can be incorrect, misleading or outdated. Please get in contact with us via a form on this page, our live chat or via email with content@seibert.group if you are in doubt, have a question, suggestion, or want changes from us.