-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
2.2.6
-
JIRA 4.3.2 + CROWD 2.2.6
-
12
-
Severity 2 - Major
-
44
-
We have a running JIRA instance and started evaluating Crowd as directory service for JIRA.
We are using JIRA as a help desk system and have extended it with custom user properties (telephone number, user location, ...) using a LDAP plug-in (https://plugins.atlassian.com/plugin/details/16524). The custom properties are displayed on the user profile and issue screen.
With JIRA 4.3 Atlassian revoked the support for OSUser so we can't use the plug-in anymore.
We have set up CROWD and defined custom user attributes (telephoneNumber), but these attributes are not synchronized into JIRA.
*Is there a possiblity to defined custom user/group attributes in CROWD and use them in JIRA?
*Why is it not possible to define a "Delegated Authentication Directory" and specify LDAP attributes automatically retrieved from the LDAP server and stored in the CROWD/JIRA database?
- is related to
-
CWD-4277 Support extended LDAP attributes in Crowd/JIRA/Confluence
- Closed
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
-
- Closed
-
-
- Closed
-
- Future Consideration
-
- Not Being Considered
- is cloned by
-
KRAK-4558 Loading...
[CWD-2417] CROWD - JIRA integration does not synchronize custom user attributes / LDAP attributes
We have our Jira having its user credentials mapped to LDAP.
Can we have an option to benefit sorting of users based on the certain categories (say business units). The information of business unit is available in LDAP, so can we pull that information into Crowd.
We would really need this feature to generate a report of which team has how many users based on the business unit category to which they belong.
Please update us if you have an option to generate users report with this information.
Thanks,
Sreedevi
Karie Kelly
added a comment - This is an issue for us as well. The benefit of Crowd is managing users is a single location. If properties are not shared, we lose value and our data becomes suspect because you are relying on someone manually updating these properties in both locations...which often is not done. We would really like to be able to sync these properties from Crowd to JIRA so that we can use them as the JIRA user properties are critical for our workflows.
Karie Kelly
added a comment - This is an issue for us as well. The benefit of Crowd is managing users is a single location. If properties are not shared, we lose value and our data becomes suspect because you are relying on someone manually updating these properties in both locations...which often is not done. We would really like to be able to sync these properties from Crowd to JIRA so that we can use them as the JIRA user properties are critical for our workflows. Creating a user in JIRA via UserUtil.createUserWithNotification(...) into a Remote Crowd Directory works as expected (user is in Crowd and in JIRA)
BUT:
- JIRA still handles its own exclusive user properties stored somewhere in the property* tables
- calling DirectoryManager.storeUserAttributes() on a user from a Remote Crowd Directory works with the cwd_user_attributes table inside the jira-scheme - no sync into Crowd
- Crowd has its own user attributes stored in the cwd_user_attribute table - no sync into JIRA
Before JIRA 4.3 there was one place in jira for properties and one in crowd for attributes. Now we have a third one...
Idea:
- migrate jira user properties into jira attributes respecting the directory of the user
- DirectoryManager.storeUserAttributes() should work in the given directory (the same way as UserUtil.createUserWithNotification does).
- Sync the user attributes from crowd into jira
61 customers voted and 7 years later we are still asking for basic attribute sync... Not to mention that Atlassian acquired StatusPage three years ago and has not integrated StatusPage login with Crowd. I have to wonder if Atlassian is serious about Crowd as a solution...