We have Quality Center 9.0 SE (Patch 18). One of our usernames became defunct. The only way I was able to get around it was to go directly into the database and change the username that it was locked out with to a valid username. We use LDAP for authentication, so once the username was removed from our network login, it was inacessible. My problem is fixed, but I wanted to know if there was a more 'succint' way to fix this issue.
Actually, the problem hasn't been solved. I thought this fixed it, but it looks like it goes deeper with VCS (I should have thought of that) and it actually goes to the folders that it is checked out to on the server, et al.
So, my Hack didn't work, which is unfortunate for the time being, but probably better over time.
If you are a site administrator, you can modify the Domain authentication parameter of the disabled user to point to a valid Administrator's id. I mean your username will be <old user whose id is disabled> but domain auth will be that for the valid user. So when you login, you will be logging in using old user's id, but password will be for the administrator's id. Although this is anotehr type of a hack, this may be allowed if you are an administrator and you do not have any other option.