-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
Hi everyone,
Thank you for your votes and comments on this improvement request. Whilst this is something we would like to implement some day, it is not at the forefront of our upcoming backlog.
We will be focussing on improving the integration of Crowd within our Atlassian suite of products, as well as simplifying and improving the overall user management and a unified administrative experience.
If our backlog changes and this improvement request becomes a priority, this ticket will be updated. If you'd like to better understand how we make roadmap decisions, have a read of : https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy
Cheers,
Helen Hung
Atlassian Product Management
At present, Crowd displays very basic user attributes for LDAP directories. It would be great if we could provide a screen that would allow admins to choose attributes for display in Crowd.
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
- relates to
-
- Closed
-
- Closed
- mentioned in
-
Page Loading...
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CWD-1287] Provide ability to choose user attributes for display in LDAP directory
toomellow1 the summary of this issue remains accurate: we are not working on this issue, and we have no plans to work on it in the short to medium term. (context: I'm a developer on Crowd.)
Mike Robertson
added a comment - Can someone from Atlassian comment on whether this issue (and the many related issues) are any closer to being addressed in an upcoming release?
Mike Robertson
added a comment - Can someone from Atlassian comment on whether this issue (and the many related issues) are any closer to being addressed in an upcoming release? Jira and Confluence are already supporting user attributes but Crowd doesn't and this should be the first place to add support for user-metadata. AD/LDAP contains lots of useful information, like position, departments, email aliases, photo, office location,... which are all important.
FWIW, we are currently evaluating Crowd, and without this functionality, it isn't something I can recommend that we purchase.
We would like to use it to:
- Manage the phone number in LDAP
- Manage the office location of employees
- etc.
Without this, we can in fact not use Crowd to manage users...
I agree this would be a great feature. We're integrating Crowd into our own internal intranet and currently we have to call into Crowd to authenticate and then query Active Directory over LDAP to retrieve the user's mobile number. Having this attribute available through Crowd would simplify our code base.
This would be a great addition to Crowd. Seriously.
watching and voting for this and CWD-583 now.
Brad Mace
added a comment - The only reason I haven't already recommended to my boss that we purchase Crowd is that it seems to assume LDAP is only for authentication. If I could customize the Add User screen by selecting additional attributes to prompt for, and display them with non-LDAP labels suitable for HR people, Crowd would be a no-brainer for us. Maybe some checkboxes for determining which objectclasses users get too.
Brad Mace
added a comment - The only reason I haven't already recommended to my boss that we purchase Crowd is that it seems to assume LDAP is only for authentication. If I could customize the Add User screen by selecting additional attributes to prompt for, and display them with non-LDAP labels suitable for HR people, Crowd would be a no-brainer for us. Maybe some checkboxes for determining which objectclasses users get too.
Are there any plans to implement this feature?
We use Crowd for all of our systems and every information about a user is stored in the LDAP.