The atlassian-user framework uses diplayName to represent the full name of a principal, ie. user creations / updates to full name will propogate through as displayName changes in Crowd.

The JiveForums integration uses a concatenation of firstName and surname attributes to form the full name.

This currently causes conflicts when a user is created via Confluence for example, and then retrieved via Jive.

The behaviour should be similar to what is implemented in the Crowd Console:

1. Searching for full name: if displayName attribute exists, use it; otherwise concatenate firstName and surname attributes and return it.
2. Adding/updating full name: update both displayName and firstName/surname attributes.