Garen
Senior Member
Joined 12 years ago
User Profile
User Widgets
Contributions
Re: Non-expiring internal accounts for scripting when external authentication is utilized
The ability to use a local admin account is very common with other tools, and is also needed if the local LDAP configuration is inadvertently broken, or the LDAP directory is down. All of these use cases would be greatly helped by the ability to use a local admin account when an external directory is configured.6.6KViews0likes0CommentsCollaborator needs ability for administrators to merge accounts
One fine summer day, "Jane Smith" (sAMAccountName/username == "janesmit") gets married, and changes her name to Jane Johnson. After returning from her honeymoon and going back to work, she logs into her computer and other applications as "janejohn", and all is well. Unfortunately, when she logs into her company's instance of Collaborator (which uses LDAP Auth) as "janejohn", it is as if she has an entirely new account - the old account "janesmit" is separate, and she no longer has access to the reviews associated with her old account ("janesmit"). Collaborator does not act appropriately when accounts are renamed. Jane is understandably not happy, and writes an email to the maintainers of Collaborator at her company, asking for the accounts to be merged. Unfortunately, Collaborator provides no such capability to the administrators of the tool, and Jane is sad. If only SmartBear would add the ability for an administrator to merge accounts, Jane would be happy. :)15KViews9likes6Comments