-
Suggestion
-
Resolution: Duplicate
-
None
-
None
I would like very much to see extended LDAP attributes supported in future Crowd versions.
Currently, Crowd (and all the tied-in Atlassian applications like JIRA, Confluence and Bamboo) have to rely on user to enter their attributes in the database by themselves. But why bother if we (usually) already have them in our LDAP directories?
The usual attributes we're using at our company are:
- telephoneNumber
- mobile (That's for the cell phone, obviously)
- jpegPhoto
- title (Job Title)
- manager (that's for the person's immediate supervisor)
I'm sure there will be other people that'd like very much for Crowd/JIRA/Confluence to support this, as entering that manually was always an unneeded and cumbersome task.
Anyway, thank you for your time Atlassian, you're doing a great work!
[CWD-4277] Support extended LDAP attributes in Crowd/JIRA/Confluence
Workflow | Original: JAC Suggestion Workflow [ 3363040 ] | New: JAC Suggestion Workflow 3 [ 3626364 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1393179 ] | New: JAC Suggestion Workflow [ 3363040 ] |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 838214 ] | New: Simplified Crowd Development Workflow v2 [ 1393179 ] |
Assignee | New: Paz [ jpaz ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Description |
New:
I would like very much to see extended LDAP attributes supported in future Crowd versions.
Currently, Crowd (and all the tied-in Atlassian applications like JIRA, Confluence and Bamboo) have to rely on user to enter their attributes in the database by themselves. But why bother if we (usually) already have them in our LDAP directories? The usual attributes we're using at our company are: * telephoneNumber * mobile (That's for the cell phone, obviously) * jpegPhoto * title (Job Title) * manager (that's for the person's immediate supervisor) I'm sure there will be other people that'd like very much for Crowd/JIRA/Confluence to support this, as entering that manually was always an unneeded and cumbersome task. Anyway, thank you for your time Atlassian, you're doing a great work! |
Environment |
Original:
Hi.
I would like very much to see extended LDAP attributes supported in future Crowd versions. Currently, Crowd (and all the tied-in Atlassian applications like JIRA, Confluence and Bamboo) have to rely on user to enter their attributes in the database by themselves. But why bother if we (usually) already have them in our LDAP directories? The usual attributes we're using at our company are: * telephoneNumber * mobile (That's for the cell phone, obviously) * jpegPhoto * title (Job Title) * manager (that's for the person's immediate supervisor) I'm sure there will be other people that'd like very much for Crowd/JIRA/Confluence to support this, as entering that manually was always an unneeded and cumbersome task. Anyway, thank you for your time Atlassian, you're doing a great work! |
Thanks for the feedback, and the specific use cases that would benefit you.
A lot of this is covered by existing issues (CWD-1287, CWD-3196), so I'm going to resolve this as a duplicate to focus attention on those issues.