tamer wrote:

is this restriction still valid?

The restriction is still there. You can archive users but not delete them.

if yes, what's the reason for not allowing to delete users?

One is technical. There may be lots of references to the user in the
repository, such as work items comments and change set owners. If a
user were completely removed from the repository, then all those
references would have to be cleaned up, or RTC would have to be able to
gracefully handle dangling references.

The other reason I can think of has to do with preserving audit trails.
Even though an employee has left the company and should no longer have
access to the repository, I still want to keep a record of what he did
(the change sets he created, the work items he resolved, etc.) when he
was an employee. Deleting the user account rather than archiving it
would lose that information.

You cannot remove the users.

You can instead change it to a user id that is present in ldap.

--- Balaji

Hi,

During 'Setup User Registry', I choose Non-LDAP Registry as user management method.

I added two users, now I found that I can't delete them, It can only be archived. How to completely remve users ?

Thanks and Best Regards,
Hamouda

is this restriction still valid?
if yes, what's the reason for not allowing to delete users?

David Olsen wrote:

tamer wrote:
is this restriction still valid?

The restriction is still there. You can archive users but not delete them.

if yes, what's the reason for not allowing to delete users?

One is technical. There may be lots of references to the user in the
repository, such as work items comments and change set owners. If a
user were completely removed from the repository, then all those
references would have to be cleaned up, or RTC would have to be able to
gracefully handle dangling references.

The other reason I can think of has to do with preserving audit trails.
Even though an employee has left the company and should no longer have
access to the repository, I still want to keep a record of what he did
(the change sets he created, the work items he resolved, etc.) when he
was an employee. Deleting the user account rather than archiving it
would lose that information.

These reasons make sense, and in general I agree with the logic, but
with one big caveat. If, upon installing RTC you make the fatal mistake
of running through the tutorials (and what could be more natural than
that?), you will find yourself with large volumes of fictional users
which were automatically imported by the tutorials. In fact, six months
into our experience with RTC, we still have more fictional users than
real ones. These people come with pictures and everything - they look
real. Heck, they look like competent, likable people, the kind I'd love
to work with (especially Marlene Stamp, hubba hubba!).

But seriously, these are not real people and they've never been
associated with any real work. It's quite annoying to have to deal with
them forever simply because someone on the team made the mistake (!) of
doing the tutorials.

Would it be possible to do reference counting on users, such that they
can be removed only if nothing references them? Or maybe an "oops"
window - say, that artifacts can be removed in the first 48 hours, maybe
a week, after creation (where time in the archived state doesn't count)?

Or maybe an even deeper dungeon than "archived" called "deleted"? I'm
thinking of a place where things cannot be retrieved; there would be no
"show deleted" checkbox. If some live artifact shows a reference to a
removed item then fine, but there's no other way to find or show it.

MK

At a minimum, there should be a way to "archive" a user, so that it no
longer appears in selection menus. I've submitted work item 87496 for this.

Cheers,
Geoff

Mervyn Keene wrote:

David Olsen wrote:
tamer wrote:
is this restriction still valid?

The restriction is still there. You can archive users but not delete
them.

if yes, what's the reason for not allowing to delete users?

One is technical. There may be lots of references to the user in the
repository, such as work items comments and change set owners. If a
user were completely removed from the repository, then all those
references would have to be cleaned up, or RTC would have to be able
to gracefully handle dangling references.

The other reason I can think of has to do with preserving audit
trails. Even though an employee has left the company and should no
longer have access to the repository, I still want to keep a record of
what he did (the change sets he created, the work items he resolved,
etc.) when he was an employee. Deleting the user account rather than
archiving it would lose that information.

These reasons make sense, and in general I agree with the logic, but
with one big caveat. If, upon installing RTC you make the fatal mistake
of running through the tutorials (and what could be more natural than
that?), you will find yourself with large volumes of fictional users
which were automatically imported by the tutorials. In fact, six months
into our experience with RTC, we still have more fictional users than
real ones. These people come with pictures and everything - they look
real. Heck, they look like competent, likable people, the kind I'd love
to work with (especially Marlene Stamp, hubba hubba!).

But seriously, these are not real people and they've never been
associated with any real work. It's quite annoying to have to deal with
them forever simply because someone on the team made the mistake (!) of
doing the tutorials.

Would it be possible to do reference counting on users, such that they
can be removed only if nothing references them? Or maybe an "oops"
window - say, that artifacts can be removed in the first 48 hours, maybe
a week, after creation (where time in the archived state doesn't count)?

Or maybe an even deeper dungeon than "archived" called "deleted"? I'm
thinking of a place where things cannot be retrieved; there would be no
"show deleted" checkbox. If some live artifact shows a reference to a
removed item then fine, but there's no other way to find or show it.

MK

After reading some other posts on this topic, I've resolved my problem. In the advanced properties section of the Jazz server, I changed my User Registry Type to "Unsupported", renamed the user ID in User Management, and changed my user registry type back to "TOMCAT". I then added the original ID as a new user. The user ID now works fine.

Here was my original post:

On error in setting up RTC 2.0, I also selected "Non LDAP external registry" and created a new user. When I tried to login with this user ID, it was apparent that the external registry setting was an incorrect choice. I have since set the user registry correctly to "Tomcat User Database". All of my ID's that I've addded since then work fine, but the one ID added when the external registry setting was set, I can't seem to use or modify. I'd just like to delete the user ID and add it again, but of course Jazz won't allow it. When I try to edit that user in the user console, I receive the message:

"This user was not found in the directory service. This user will not be able to login unless they have an account in the directory service."

We need to keep this user ID. How and/or where can I "fix" it so it will stop looking for an external registry that never existed and start using the Tomcat registry as all my other ID's are using?