I am currently working to prove out TEM 8.2 in my DEV environment, with adding it to production very soon.
I have one significant issue. I created my TEM users using the same account as thier AD accounts, and two accounts of the same name can’t occupy the same space.
Some of these accounts have ownership of a lot of content (including my master operator account). I am looking for the best way to utilize LDAP for everyone, yet no lose all signatures to the content.
This may not be possible, but I really am interested in how anyone else has handled this.
I talked this over with IBM support. It appears that the previous account (non-LDAP) needs to be removed if it shares a common name. That users content is then re-signed under a master operator account. When you re-add that user as the LDAP account, they should be able to manipulate thier custom content with the appropriate rights. Unfortunately you lose the history of the content that user did own.
I have yet to put 8.2 into production (have it in DEV). I imagine when I get it into production, I will move slowly to migrate current TEM users to change over to thier LDAP accounts, and see what happens with the content/ actions of thier previous account (the PVK account).
I just upgraded our development environment to 8.2 today and I will have the same issue when migrating users from the old account to using LDAP. Do you have an estimated ETA when the latest version will be released that will correct this?
Version 8.2.1175 and later consoles should provide the ability to right click on an existing user and select “Convert to LDAP Operator”, which I think is what you’re looking for here.