Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1320

Email user login details when their account is created in Crowd.

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      When an account is created by an administrator, have the following options:

      • email temp password
      • link to the administration console with requiresPasswordChange set to true, allowing admins to force a password reset.

            [CWD-1320] Email user login details when their account is created in Crowd.

            Any progress .......  @atlassian? Created:17/Nov/2008 .... Last status update October 2013 ...... 

            Daniel Piculjan added a comment - Any progress .......  @atlassian? Created:17/Nov/2008 .... Last status update October 2013 ...... 

            naeimeh mhm added a comment - - edited

            Is there any update on send email when a new user create in crowd? as well as jira

             

            naeimeh mhm added a comment - - edited Is there any update on send email when a new user create in crowd? as well as jira  

            bn273340 added a comment -

            Can we get an update on this please?  This is becoming a large enough of a hassle for our ecosystem we are considering dumping Crowd all together.  With close to 5000 users and still growing we need Crowd to manage invites and inactive users for us.  Crowd is our primary identity management solution outside of the corporate firewall.  We are not allowed to have it hooked to the internal AD/LDAP servers.  Crowd doesn't just provide authentication for Atlassian products.  We leverage for a dozen or so other in-house applications as well.  The user creation for these applications is becoming a very large support overhead for us.

            bn273340 added a comment - Can we get an update on this please?  This is becoming a large enough of a hassle for our ecosystem we are considering dumping Crowd all together.  With close to 5000 users and still growing we need Crowd to manage invites and inactive users for us.  Crowd is our primary identity management solution outside of the corporate firewall.  We are not allowed to have it hooked to the internal AD/LDAP servers.  Crowd doesn't just provide authentication for Atlassian products.  We leverage for a dozen or so other in-house applications as well.  The user creation for these applications is becoming a very large support overhead for us.

            Any progress on this request?  I set requiresPasswordChange to true and now it won't let the users login at all now.  

            Angie Zeller added a comment - Any progress on this request?  I set requiresPasswordChange to true and now it won't let the users login at all now.  

            bn273340 added a comment -

            Any progress or at least a Yes/No answer?  As our user base keeps growing and Crowd keeps meandering towards the useless category without this feature.

            bn273340 added a comment - Any progress or at least a Yes/No answer?  As our user base keeps growing and Crowd keeps meandering towards the useless category without this feature.

            JP added a comment -

            any progress on this?

            JP added a comment - any progress on this?

            This is, indeed, a missing core feature. I'd say the external user importer (csv for instance) is useless when you're dealing with new users since you still have to send them the password separately.

            Ludovic Roguet added a comment - This is, indeed, a missing core feature. I'd say the external user importer (csv for instance) is useless when you're dealing with new users since you still have to send them the password separately.

            I was really hoping this would get fixed in v2.8...

            One can only hope it is fixed in v2.9 yet with this issue being open for almost 6 years that's a long shot.....

            Benjamin D. Smith added a comment - I was really hoping this would get fixed in v2.8... One can only hope it is fixed in v2.9 yet with this issue being open for almost 6 years that's a long shot.....

            I cannot implement this because of the plethora of emails I will receive from clients complaining why they cannot login. I would have to do some research to first identify the problem (maybe they forgot their password or maybe they do not have access to that particular application). I cant see how to implement password complexity without notifying users that their password has expired.

            This should be fixed.

            Salvador Velazquez added a comment - I cannot implement this because of the plethora of emails I will receive from clients complaining why they cannot login. I would have to do some research to first identify the problem (maybe they forgot their password or maybe they do not have access to that particular application). I cant see how to implement password complexity without notifying users that their password has expired. This should be fixed.

            prdonahue added a comment -

            I really hope development on Crowd is still ongoing – along with an effort to standardize the deployment and integration of it along with products like JIRA, Confluence, etc. It's clear that the internals are disjointed, perhaps the result of acquisitions or entirely different teams building without integration in mind. Adding some basic user management capabilities to Crowd such as this would streamline the IT operations of many companies.

            prdonahue added a comment - I really hope development on Crowd is still ongoing – along with an effort to standardize the deployment and integration of it along with products like JIRA, Confluence, etc. It's clear that the internals are disjointed, perhaps the result of acquisitions or entirely different teams building without integration in mind. Adding some basic user management capabilities to Crowd such as this would streamline the IT operations of many companies.

              Unassigned Unassigned
              justen.stepka@atlassian.com Justen Stepka [Atlassian]
              Votes:
              121 Vote for this issue
              Watchers:
              71 Start watching this issue

                Created:
                Updated:
                Resolved: