I'm wondering why such fundamental and basic functionality (similar to the page name issue) is not addressed for more than 10 years (as of CWD-1287). But the user interface (which was fine many years ago) has been redesigned every year and gets cluttered with nice to have features.

This is also impacting ability to allow users to update profile info
https://jira.expedia.biz/browse/EITPO-4956 

As an answer to always changing organizations, I made a central confluence page with contact information about teams and employees.
I link to this central "team page" from other pages, so I can update team assignments easily.
On this central "team page", I show the mail adress (@....) and the phone numbers of the staff.
At the moment, I have to change the phone numbers manually: annoying.
So I'm interested in getting the phone numbers from LDAP - possible ?

Unbelievable this is still an issue.

Makes me second guess drinking the Atlassian koolaid.  quite possibly time to start looking at alternatives.

This issue affects our team.

This seems like a simple functionality.  it seems to work with AD.  why not LDAP?

i dont know, feels more like a confluence funeral. Seems like Atlassian is going the "EA" or "Symantec" way in treating customers. But dont take my words. just look through the Jira tickets

This will be 11 years old come December, should we have a birthday party? 

Hi,

we're still using echocat Adam https://marketplace.atlassian.com/plugins/org.echocat.adam/server/overview

It's marked as unsupported but the author normally answers within a day. Compatible up to Confluence 6.2.4, but it's working without flaws on 6.4.1 in our staging environment.

Must have functionality!!  

As we maintain several information central in our AD we need to sync several fields also from there to confluence (picture, department, phone...). Please make this functionality possible.

It would be really helpful to have an easy possibility to synchronize some additional data to Confluence. I'm really looking forward to have that feature/improvement!

Okay, thanks!

It only working when Confluence is connected to an AD/LDAP.

We also use it for confluence, not for JIRA.
But our Confluence synchronizes the user data from JIRA.
In JIRA it's synchronized with an AD.

This is a Confluence addon. I don't know if it's available for Jira.

Anyway, the LDAP/AD configuration doesn't need to be changed. The default configuration of echocat Adam should at least show some changes below the Persons menu in Confluence. We still use Confluence 5.9.

Hey Jan-Peter Rusch,

we also tried echocat Adam, but it won't work.
Could you describe how you configured it?
Did you change anything in JIRA?

Greetings,
Lisa

echocat Adam (Check marketplace) is free and compatible with 5.9 since mid-march. Works great & allows flexible configuration to meet your needs (eg. department listings, display mobile phone # only to certain groups,...)

The latest version of our add-on now supports the synchronization of users pictures (for example, you can use the “thumbnailPhoto” attribute for Active Directory) so that it met the requirements listed above.

See the Marketplace listing for more information and try it for free: User Profiles for Confluence

If an improvement request is open, the feature/improvement doesn't exist in any version of Confluence. The affects-version in this case just reflects when we first added LDAP support.

For bugs, we just indicate the earliest affected version with the affects-version field. JIRA's version handling is a little bit limited in that it can't easily reflect a range of versions without being a big maintenance headache.

Details on our JIRA usage at Atlassian are here: https://confluence.atlassian.com/display/DEV/JIRA+usage+guidelines

could some atlassian dude please add the recent versions as affected versions? As far as I know this is still not possible in your enterprise ready latest version of confluence, right?

A free (and open source) plugin that enables this functionality is echocat Adam

The marketplace listing still shows 5.4 compatibility but we have tested and are using it on 5.5.

The Enterprise Directory and Org Chart plugin has this functionality.

This would be a great advantage, so you do not have to maintain two separate databases!

There should be a possibility to map every field of your choice to the user data...

I've written a Ruby script which copies the relevant AD fields to a user's Confluence profile:

https://github.com/jefft/activedirectory-confluence-user-profile-sync

Unfortunately it can't do jpegPhoto because admin users cannot edit a user's photo (CONF-14368).

Feedback/pull requests welcome.

http://blogs.atlassian.com/2013/07/profile-photos-matter/

Well Atlassian? 7 years later, any update on giving your users what they want? Even new businesses adopting your tools find these simple things to be crucial to adopting the systems effectively. 130+ votes say so!

Were looking for this feature and discovered this issue. I agree that such basic feature should be standard and not extra cost and effort!! We are implementing Confluence now in our business and therefore hoping Atlassian will take this into consideration as a new feature as soon as possible. It is a bit of an overhead to upload pictures for every employee on the confluence page when all pictures (++) are in AD already and Confluence is connected via LDAP.

@Matin - "please do [take a position on these requests, and be open and honest about that position]. We can cope with that." Well said. [My additions]

I do not think that Atlassian will implement this soon, it would not be a nice gesture to the plugin developers. Though i really think that such basic feature should be standard and not extra cost and effort, i bought http://www.communardo.de/home/communardo/produkte/user-profile-plugin-2/ - and this works quite well, up to simple org charts from Active Directory. But same, it would really be appreciated if Atlassian spoke clear words. This is one of quite a lot of requests where Atlassian does not take up position. Please do, we can cope with that.

Same here (need to have a stronger LDAP user information retrieval to fend off sharepoint, that provides a nice integration with user and hierarchical information).

And here another vote for this. We don't want to pay some 3rd party plugins for synchronizing phone numbers from AD to Confluence. Would be nice to see this feature integrated soon.

Duplicate data is the start of all evil ...
please provide the import of common data and the ability to present this data by using macros like { userlist }

Another vote - this lack of integration is a negative for Confluence and people here keep muttering about moving to SharePoint.

I agree with Matin - this seems like something that should come under basic functionality. Why do I have to go buy a pretty pricey plugin in order to pull information out of LDAP?

Regards

Jeanmarie

Communardos User Profile Plugin does most of the trick, and works well here - though it is not really understandable why such basic functionality demands extra cost. And what is still missing is the photo import. As Confluence goes social and more corporate intranets seem to go confluence , this shoulb be considered crucial.

Regards

Matin

This would be just the feature we are looking for.

Especially with the profile pictures..
"remember to add your profile picture to Confluence also".. I have to remind users via e-mail almost weekly. This would help "administration" of these things bit more easy. (We upload photos of our users to AD when they start their work at our company)

-Patrick

Fully agree with Jason. This feature is often requested by larger corporations which want to do something like the mysite in MS Sharepoint. Please Atlassian, go for it! We are all waiting.

One more vote for this. It would be great if this could become available for Jira as well. More so Jira for my company, but really all Atlassian products should have this feature.

I wish Atlassian would gain momentum on some of these 5+ year old issues. Truthfully I am a big fan of the plugin system but IMHO it seems like Atlassian uses it as a crutch by waiting for issues to be solved by a third party. That wasn't so bad years ago when the licensing was much cheaper, but given the current pricing scheme I think it's not unfair for paying customers to ask that requested features be integrated in less than 5 years.

Currently I am in the process of presenting Atlassian products to the company I just joined. If successful, this will be the third company I have convinced that Atlassian Jira/Greenhopper/Confluence are the right tools. I truly believe that they are. But it's so hard to convince them when they ask if it has certain functionality and I have to say "no but it was requested over 5 years ago so hopefully they'll get around to it soon". Then I try to pitch the "We could pay a developer to build a plugin" idea, but with the current license costs that doesn't work anymore.

Please put this on the roadmap soon, and add it to the Jira roadmap as well.

Can we get an update from Atlassian on this issue? What is the likelyhood that this happens in the next year?

Strategically we are attempting to eliminate maintaining the same information in several places. If we knew this was on a roadmap then that would assist with strategic planning. In terms of using Confluence as an Intranet this seems a critical integration shortcoming.

Use Case:

• Allow users to lookup/see information about other user's:
  • phone #
  • department
  • location
  • title
  • email address

• For a user to maintain their own information (update of specific LDAP attributes). Designate Confluence to be the user interface to maintain some personal LDAP attributes.

Added a vote for this as well, would be a great feature to have built into Confluence, basically would become the front end to whatever LDAP directory you are using.

People watching this issue may be interested in a couple commercial plugins recently released:

• User Profile Plugin plugin by Communardo Software GmbH and
• Enterprise Directory and Org Chart for Confluence by AppFusions

Here's another vote for this feature.
We're trying to get rid of Basecamp since the only thing we're currently still using it for it is the people directory.
Can't this feature be added in the form of a plugin? Sounds like something that shouldn't be that difficult, although I'm no Java developer so little do I know

This improvement is currently unscheduled, so I'm sorry to say that we don't have an estimate on when it will be implemented. However, we are working on infrastructure improvements to user management for LDAP nested groups (CONF-17150) which will make this feature easier to implement and therefore much more likely to be done in the long term.

This is really important for our customer. Is there any planning, when this will be implemented and released?

This would also be tremendously useful to us. Voted for it. Please implement!

This is something we are really looking for. We are feeding our LDAP with information directly from our PS HR system. Therefore there is up-to-date accurate information on people, i.e. job description, location, etc, etc. What has been lacking is a tool to display this.

We would love Confluence to be that tool. We would like to do the following in Confluence,

• Specify what additional LDAP fields are exposed in Confluence (read-only),
• Specify what additional LDAP fields are exposed in Confluence (read and write).

I agree with robert dahlbord on promoting crowd (we use crowd on another product also, even fixed some of its issues), the info is in ldap and easy to retrieve, why not spend some time implementing this.

Since this issue affect version 3.0 as well, could someone please update the list of affected versions. I guess its more likely to get this fixed in the latest release. Btw, Promoting Crowd by forcing users that requires this LDAP improvement seems a bit odd to me. Anyway, just my thoughts. //R

Adding another vote for this. The new user profile in 3.0 is great, but it would be way better if we could get more of the info in there from the LDAP/Active Directory integration. The fields in the "Company" section in particular would make a lot of sense.

Don: unfortunately not, so this issue remains open. You can see the list of issues resolved for Confluence 3.0 on our release notes page:

http://confluence.atlassian.com/display/DOC/Confluence+3.0+Release+Notes

Sorry for the delay in getting back to you.

Has this functionality been implemented as part of Confluence 3.0?

We might consider adding this feature into our SSO product, Crowd, and offer crowd as a plugin for Confluence and JIRA at a reasonable price. This is work that is being considered this year. Stay tuned.

If you're interested to know how we decide on which features to implement, please read this:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

With 800 users heading to over 1000 further LDAP integration is really needed for Confluence, Especially to enable people to find each other and their details.