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.

Export and Import locations for users?

sacco

Here in the Wiki it is suggested that users can be Imported & Exported
to/from the repository store: user://alfrescoUserStore

http://wiki.alfresco.com/wiki/Export_and_Import#Default_Stores

But here, it says:

People are imported into the special location /sys:system/syseople

http://wiki.alfresco.com/wiki/Export_and_Import_View_Schema#Schema_Examples

Does anybody know which is correct?

Find more posts tagged with

Comments

sacco

In the case that the latter is correct, there appears to be another problem:

A user can be imported and appears to now exist on the system,
however, when admin selects the user to change the password
(as there doesn't appear to be a way to import passwords),
the baffling result is:

  
Please correct the errors below then click Finish. 
A system error happened during the operation: User name does not exist: mytestuser
‍‍‍‍

Is this a known bug?

andy

Hi

We have split "user information" into Person and User. All authentication backends will end up with a Person object in the repo. They can be imported from LDAP. Only the Alfresco authentiation backend creates Users. Person objects do not carry any authentication details - just a uid. The User object in Alfresco has the password hash etc.

When external authentication systems are used they are read only. They can be used for authentication but there is no support to change credentials. You can not add a user, change the password, remove a user or do anything else except authenticate. Authentication is always passed through to the back end - it is never cached etc. Passwords are never imported. There muist be some other way to manaage users - not via Alfresco.

If Alfresco is to be used to manage users in an external system, you will have to implement the DAO to support this (instead of using the default DAO that rejects all changes and throws an exception). Your DAO will need admin rights to your authentication system by some means.

In the UI, a delete will delete the person and user from the DAO (the do nothing DAO can be configured to ignore this or throw an error). In the UI changing the password will go to the DAO - it does not know what to do and will reject it. It can be configured to ignore it - but the password will not be changed.

How would users normally change their password for your authentication system?

Andy