Page MenuHomePhabricator
Create Task
Maniphest T10383

auto link account / require multiple accounts
Closed, DuplicatePublic
Actions

Description

In our environment we require two accounts be linked:

  • a custom oauth provider that we implemented internally
    • used for for registration, login, email, full name, etc.
  • jira
    • used for the jira integration

We'd like to do something on the order of one of the following

  1. trust usernames across services so that the Jira linkage flow isn't required
  2. add a "mandatory to link" step to the Jira username
  3. ideal: pre-create user accounts linked to jira accounts

It is suboptimal for us to expect that every developer find the "link external account" flow and link their Jira account. This is particularly true since all other accounts are pre-created for engineers and this adds a bit to the new user onboarding.

Related Objects

Event Timeline

eadler created this task.Feb 18 2016, 7:54 PM
eadler moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Feb 18 2016, 7:57 PM
avivey added a subscriber: avivey.Feb 18 2016, 8:18 PM

I've had the same issue in previous install - I ended up using the Setup Issue UI to push users in the right direction; It worked, but it was a small-scale install.

One problem with automagically linking accounts is that we actually need a valid oauth token (For JIRA integration), and it should actually belong to the user; So to get it to work, you also need to bypass some security in the JIRA side (Or force the user to go through the motions).

A cheap work-around is to only use JIRA for registration, and assume that the information in JIRA is synced to the "master" user registry.

(The user's JIRA token is used both to read the ticket information, and to update the link/message in jira).

epriestley added a subscriber: epriestley.Feb 18 2016, 8:33 PM

A custom dashboard panel (that checks if the user has JIRA linked, gives them a big annoying flashing GIF "LINK YOUR JIRA ACCOUNT!!" button if they don't, and renders nothing if they do) on a custom homepage dashboard might be a similar achievable approach without an unreasonable amount of effort, given the technology of today.

I'd also expect that users are mostly only inconveniencing themselves slightly if they don't link JIRA right away, so this might not be too important to enforce universally? What are you concerned about if a user doesn't link their account immediately?

eadler added a comment.Feb 18 2016, 9:10 PM

A custom panel might be a good solution. Our primary concern is the lack of discover-ability of (a) the ability to link Jira bugs with Differentials and (b) the mechanism to link a jira account with the phabricator account

A secondary concern is that we don't want users to have to go through any new user registration flow. We're working on automatically creating accounts for users for example.

eadler moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Mar 9 2016, 10:11 PM
eadler closed this task as a duplicate of T8629: Create some kind of queue of profile/settings action items for users.Mar 24 2016, 8:22 PM

This would be fully solved with T8629 so I'm just going to close it :/

Phabricator · Built by Phacility