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.

Cannot delete users....

stuartmcmahon

hi,
I was running 1.4 build 54 but it was causing problems so now I've installed 1.3 but I cannot delete users.

Getting the following error…..

Unable to delete the User object associated with the Person. This is not an error if an external authentication mechanism such as NTLM was previously active.
Failed to delete User due to error: Transaction has been rolled back because it has been marked as rollback-only

Anybody know why I can't delete users?

thanks,
Stuart.

Find more posts tagged with

Comments

gotheek

I have the same problem.

We have LDAP configured within Alfresco.

Users log on through the web interface to register their user within the system, based upon the LDAP system that covers the rest of the network.

Try to delete a user and I get the following error message:

Unable to delete the User object associated with the Person. This is not an error if an external authentication mechanism such as NTLM was previously active.
Failed to delete User due to error: Transaction has been rolled back because it has been marked as rollback-only

I can only assume that since LDAP and Alfresco have entered into a marriage and anything that is communicated between them becomes a part of the joint assets.

I've marked the users as "Delete" and the only way I can think to get rid of them is to get into the MySQL database and do it through that.

However, I'd love an alternative approach.

Anyone…?

jgreen

I had a similar problem, in my experiments with NTLM integrated suthentication, I managed to create duplicate users. It was relatively easy to hunt down the records in MySQL that were the issues then delete the records and all thier relationships.
However, it appeared after a little more digging that it had corrupted the DB by leaving the ID's Preferences around. Most of alfresco worked just fine, but some Lucene queries that should have run generated exceptions. Since this was a R&D Instance we decided to let it be through testing and are going to start from scratch in production.

andy

Hi

The Default DAO has been extended to support deleting people from alfresco without trying to delete users in LDAP. This should solve this problem.

Users with the same UID will cause a problem with queries. There is no integrity constraint for this - it is enforced via the services.

Via LDAP sync, it is possible to load two new users with the same ID.
If the user exists - it will update the existing user. There is an outstanding issue to investigate/detect this case during LDAP sync.

Regards

Andy

stuartmcmahon

Hi Andy,
I am using 1.3 - has the Default DAO entension you refer to been implemented in this release or the next.
I am using org.alfresco.repo.security.authentication.ntlm.NullMutableAuthenticationDao
as the LDAP authenticationDao.
I'd rather not move to 1.4 until the final release.

Stuart.

andy

Hi

The fix I mentioned is in 1.4 code line.

Also make sure your uids in the LDAP repository are unique.
This is not enfoced during the import but is required and will result in an error as multiple person objects will have the same userId.

Regards

Andy

stuartmcmahon

Hi Andy,
I just installed 1.4RC1 as a trial.
However, I still cannot remove users that have been inserted into the database at first logon after authentication via NTLM\LDAP.

Perhaps the fix is not in 1.4RC1.

rgds,
Stuart.

andy

Hi

I am not sure when this went into the community release.
It could be the next drop.

Regards

Andy