We recently deployed Crowd to manage access to our various Atlassian applications. We're having a workflow issue with our users. Every time a user needs to change their password this happens:
1. user requests password reset.
2. helpdesk uses Crowd to generate reset email.
3. user resets password by following link.
4. user finds themselves at the Crowd login prompt.
5. user tries to login to Crowd and it fails. They contact the helpdesk to say their password reset didn't work.
6. helpdesk and user spend 15 frustrating minutes trying to figure out what's wrong.
7. helpdesk realizes the user is trying to log into Crowd instead of Confluence or Jira.
I understand what's happening - the user is trying to log into the wrong application, and they aren't authorized to use Crowd. But this is creating a bad user experience. And its happening on almost every password reset for any non-technical user. (Technical users still encounter the issue, but recognize they are at the Crowd login screen and are able to connect the dots.)
Is there a fix for this? It's very confusing for some of our users, and busting an otherwise successful rollout. Am I just supposed to tell users, "here's your Crowd account, but you can't login to Crowd. So reset your Crowd password, don't log into crowd, and do a 'u-turn' if you reach the crowd login page."
