Sugar 14; has lost the ability to set a User Password

It appears it is no longer possible to set a user password within the UX; the Release Notes do not mention that the ability to set a password has been removed.  https://support.sugarcrm.com/documentation/sugar_versions/14.0/ent/sugar_14.0.0_release_notes/#User_Interface

We do not have an outbound email server setup. Until we upgraded to Sugar 14, this was a non-issue. How can we set a user's password in Sugar 14?

We are on-premise and not using Sugar Identity. 

  • Hi Jeff,

    Thank you for your question! The option to set a password in the UI is no longer available. In it's place is the ability to reset a user's password via the user's action menu. Selecting this option prompts a password reset email to be sent to the user. This update does require the system email to be set up. Please refer to the following pages that explain more about the updated Users module:

    What to Expect When Upgrading to 14.0 (Q2 2024)
    User Management

    Please let me know if you have additional questions!

    Jamie

  • Hi Jeff, I guess the only other option if configuring an email account is not possible (due to firewall etc) - then you can change the hashed PW on the database to gain access. Then log in as that user and reset the password from the UI.

  • Without the ability to send a user an email; how do you propose activating a user? We do not have SMTP configured.

  •   ,

    thank you for your suggestion. This would require access to the database; which our administrators do not have. There should be a sugar_config option to turn this functionality on/off. There are a lot of undocumented configuration options.

  • The UX for the Change Password screen is not usable. Have you looked at it?

    How is the user supposed to know what to do?

    There are no borders on the fields
    Why is the field User Name visible?


     https://postimg.cc/JsSjGj7j

  • I just wanted to share that this is a reported issue, #94980, for anyone who might come across this thread in the future. If anyone is affected by this issue, I recommend contacting Support with that issue number to help track the impact.

    Thanks!

    -Brenda

  • We have a sugar v14 instance with LDAP authentication, we used to use local PWD to impersonate users when necessary such as in our DEV environment to test things as a user with different Roles/Teams or in our PRD environment for debugging instances where a single user has issues working in Sugar.

    Without SugarIdentity, how can an admin impersonate a user?

    Thank you,
    FrancescaS

  • Hi  ,

    We have a plugin, Upsert Sudo, that is popular with self-hosted customers that enables the ability to impersonate users. We also have customers in SugarCloud use Upsert Sudo because they find that the impersonate feature in SugarIdentity to be cumbersome in the following ways:

    • Admin users cannot easily impersonate a user to validate their experience with a specific record or module because they need to open a new tab, go to SugarIdentity, find the user, click 'Impersonate', and then go back to the tab that had the page loaded. With Upsert Sudo, you select the 'Sudo Log In' feature directly from your profile menu, choose the user, and the current page is immediately refreshed to reflect the experience of that user. It is a big time saver for admins who spend a lot of time configuring and troubleshooting issues for users where team and role security introduce variable experiences.
    • Once an Impersonate session is completed with Sugar Identity, the only way to complete the Impersonate session is to click 'Finish Impersonating' which closes out the current browser tab. If any other Sugar tabs are open, the admin then needs to go to one of those tabs and refresh manually for their original session to be restored. With Upsert Sudo, completing the session is done from the profile menu and all open tabs are automatically reverted to your original session. 

    Let me know if you would like a more in-depth demo of the plugin!

    Chris

  • The documentation says the following, isn't that correct any more?

  • Hi  ,

    I think that works if you are changing your own password but in my case we have LDAP users and we would like Admins to be able to impersonate them in our development environment. 

    Admins used to be able to set a local password for the user, but that is no longer true. And without Sugar Identity we can't "impersonate user".

    I did notice that for users who had a local password before the upgrade of my DEV environment to v14 that password still works and because we are on site and I have access to the DB I can use a sql statement on my DEV environment to set the user password to something my testers can use the same way the admin password can be reset:

    support.sugarcrm.com/.../