While I’m not sure how credential subfolders were intended to work, I do appreciate credential subfolder are available. But there are some strange behaviors, for example: To get a folder to display under “Credential” root folder you must added a credential (login) entry to the folder which causes the folder to be copy to credentials root folder. That fine, but why not move it from the sessions root folder to the credentials root folder if only credentials entries exist in it? Plus if anything is modify or added to the folder properties, like a description, why create a copy of the credential subfolder under the sessions root? I have been able to delete this copy of the folder without affecting the original credential subfolder, it just create extra work for the customer.
edited by Kattywumpus on 8/10/2012
Hi,
I have entered a bug for that and I will try to reproduce it
David Hervieux
David,
Of all the issues I have submitted so far, I think this is the most important one, the others can wait. It appears any edits to add a security group or text information in the Description field for the credentials folder are lost if the folder copy created automatically under the "Sessions" folder is deleted. In our enterprise environment I need to be able to delegate management of credentials sets groups. Credentials folders would simplify setup and administration of these groups. Example; there will be several credentials sets for the Windows Administrators team and only specific people would be able to edit these credentials sets and only the Windows Administrators should be able to view these sets. I wanted to place these sets under a specific folder and set security on this folder.
edited by Kattywumpus on 8/15/2012
edited by Kattywumpus on 8/15/2012