History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-12946
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Sam Berlin
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JIRA

Better Crowd Integration Options

Created: 20/Jun/07 08:35 PM   Updated: 24/Jun/07 07:17 PM
Component/s: User Management
Affects Version/s: 3.9.2
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Anton Mazkovoi [Atlassian] and Sam Berlin
Since last comment: 56 weeks, 1 day ago
Labels:


 Description  « Hide
Please allow a new kind of user-management option that disallows manual changing that directly uses the database, but still allows functions (such as user creation or password updating) that can be forwarded to external user management programs, such as Crowd.

The rationale behind this request is that Crowd integration recommends that "External User Management" is turned on, however turning this option on removes the links on JIRA for users to create accounts and/or update passwords. These links are very useful where they're already located inside of JIRA. It would be a frustrating experience for a user to find our JIRA instance, realize they need an account to create an issue, have to navigate elsewhere to create the account, and then return back to JIRA to create the issue.

In the absence of being able to internally forward these requests to Crowd, an alternate approach would be to supply an href to JIRA in a configuration file that would cause any user-update requests to go to that link (instead of the pre-existing JIRA page).



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Anton Mazkovoi [Atlassian] - 20/Jun/07 11:52 PM
Sam,

You mean you would like to enable Signups and password changing options in the UI, such that when the user clicks those links, they are redirected to crowd?

Cheers,
Anton


Sam Berlin - 21/Jun/07 12:06 AM
That's one option that would work very well. Another would be to recognize that Crowd is being used (or another user management program) and automagically use the service for updating the user's info. Either option would be a tremendous improvement to improving third-party user-management program integration. There is a Crowd issue under CWD-306 to enable a "user self-service" app in Crowd so that users can update their information within Crowd (which would be required for the forward-to-Crowd option).

Anton Mazkovoi [Atlassian] - 21/Jun/07 11:48 PM
Sam,

Thanks for the update and clarification.

Cheers,
Anton