Jump to content

WoutDR

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by WoutDR

  1. We still notice this behavior in build 9708, any update on a fix on the way?
  2. +1 We have the same request for our environment. We noticed users that started seeing sub folders that they should not be seeing because of disabled inheritance enabled. When they create a top level folder using the basic permission model and they move the newly created folder to another top level folder that uses the advanced permission model the permissions from the top level folder are set to the sub folder that has disabled inheritance available. So if the have view permission on the top level folder but not on a folder that uses disabled inheritance, the view permission from the top level folder are forced to the folder that has disable inheritance active. This seems like something that should not be possible. This issue does not occur when we move a folder from the top level that uses the advanced permission model instead of the standard permission model.
  3. We noticed the following behavior when searching for a user when granting permission on a folder, password list or inividiual secrets. When I enter the users first name I have no problem finding that user, it show a list of matching users with their first name and surname. When we search using the surname this is also show a list of matching users with their first name and surname. When I combine firstname and surname in the search field it does show any results. Could the search field be changed so it can combine search using firstname + surname? We haven over 20000 users synced to our environment and most of our users use firstname + surname when setting user permissions.
  4. +1 for the folder\passwordlist modification\delete feature to the API. Our company is live with Passwordstate for a month now and more and more people are asking for this. Is there any ETA on this?
  5. Hi We had the same problem with version 9435, we also updated to the latest version of Passwordstate (9512) but the problem persists. After removing the Microsoft Monitoring Agent the problem was solved. We use the Microsoft Monitoring Agent for our server monitoring through SCOM and also Azure monitoring depends on this service. I hope Clickstudios can fix this problem because we currently have no monitoring/alerting on our Passwordstate servers. Kind Regards, Wout
×
×
  • Create New...