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

By default the user directories configured in Confluence (ADMINISTRATION > USERS & SECURITY > User Directories) are used to fill the user profiles.

Alternatively, you can define an XML file containing user profile data. You can find these settings under ADMINISTRATION > CUSTOM USER PROFILE > DATA SOURCES and the tab XML.

Configure the XML import

You can import additional user profile data from an XML file (e.g., exported from SAP IDM).

  1. URL or file path of a XML file with user profile data
    (warning) HTTP is recommended, other protocols like HTTPS are unsupported

    (warning) Make sure the file has the UTF-8 preamble to get special chars encoded right. Also the server should provide UTF-8 files.
  2. The XML node containing the profile data for a user
    For our example file it would be "identity" (See the example xml).
  3. XML node containing the Confluence username
    For our example file it would be "mx_user_name" (See the example xml).


Example XML file format

The XML file needs to comply with the following format:

Example XML file
<?xml version="1.0" encoding="utf-8"?> 

When the scheduled job for xml import runs, the three users defined in the xml file will be updated.

  • The fields department and team has been set for user admin. Since now, he can not edit those fields by himself anymore.

  • Only the field department has been updated for user c.norris. Since now, he can only edit the field team in his profile.

  • The fields department and team has both been set for user a.schwarzenegger. The field department has now an empty value set. Both fields can not be edit anymore by the user.

XML Profile Field

In order to use the additional profile data, you need to configure user profile fields of the type "Retrieved from XML" with the desired tag names ("department" or "team" in the example). See the CUP - Profile editor 1.16 page.

CUP: Bulk profile update (XML sync)

Then, you are ready to trigger the XML import by starting the job "CUP: Bulk profile update (XML sync)" in the scheduled jobs section of the Confluence administration interface. You can also configure the job to run regularly.

Clear XML import configuration

  • No labels

This content was last updated on 02/09/2017.

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 if you are in doubt, have a question, suggestion, or want changes from us.