nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Changing user passwords....

furtado

I have setup users on the system as contributors and editors. When those users login, they do not have any options available to change their passwords. How can it be done from the web client without logging in as admin….

Find more posts tagged with

Comments

gavinc

Unfortunately at the moment you can't.

There is a bug raised for this: http://www.alfresco.org/jira/browse/AWC-257

furtado

Thanks for the quick reply!

miranda

I really hope that this makes it into the next release… I was very surprised that it was not there, and came to the forums to find out if there was something obvious I was missing!

alarocca

Anyway, you can create it by yourself.

What you need is a jsp page with a form for input the current and new passwords. Then use API (webservice) to change the user password:

try {
AuthenticationUtils.startSession(username, oldPassword);
         AdministrationServiceSoapBindingStub admininistartionService = WebServiceFactory.getAdministrationService();
         admininistartionService.changePassword(username, oldPassword, newPassword);
         msg = "Password successfully updated.";
      } catch (Exception e) {
         msg = "Unable to update password - unknown username/password.";
         e.printStackTrace();
      } finally {
         AuthenticationUtils.endSession();
      }

Greetings,
Alessandro

mattclay

Unfortunately at the moment you can't.

There is a bug raised for this: http://www.alfresco.org/jira/browse/AWC-257

It looks like this bug is set to be fixed in release 1.3? Do you if that is the case, and when that release might occur?

Thanks.

nullman

This does not seem to be fixed in 1.3.0 Community. It is currently listed to be fixed in 1.3.1.

kevinr

That is correct, there will be a 1.3.1 release containg this and a few other minor additions to the client/server functionality.

Thanks,

Kevin