Jump to content


  • Content Count

  • Joined

  • Last visited

About Bobby

  • Rank

Profile Information

  • Gender
    Not Telling
  1. i've got a user storing the private key for a certificate in password state and they asked about storing the actual certificate in passwordstate as well. I saw there's an option to add a document to a password. From reading the docs this cert is also encrypted so it seems like a perfectly valid option. Am I missing something or is this a valid solution?
  2. For the new api access via windows account in version 8, how will that work with the number of licenses users? Will it be like the current API where it doesn’t count against the number of users or will I need to ensure I define a user for each service account that will query Passwordstate? If it’s this latter, does this mean I would need to buy more licenses users to allow API access from service accounts?
  3. Hello, Is there a way to get passwords via API and authenticate users at the same time? Suppose someone unauthorized were to get access to the scripts/code. They could run the same API calls to get passwords. (I know I can limit by IP address). Is there a way we can check authentication in an AD integrated setup so that only the specific user is able to get passwords via API?
  4. Digging up my old post here because I have a question on how this works in the new 7.7 with the new encryption keys. I upgraded from 7.3 to 7.7 and it looks like things have changed quite a bit. Do I need to ensure I have access to either the web.config file or the encryption keys zip file in order to recover? From what I can tell it looks like if I lost my web.config I would need to get the keys from the .zip file exported from passwordstate and puts keys 1 and 2 into a new web.config file. Without those keys, the db backup would be useless.
  5. Sounds good. I'll cross my fingers and try it the new way next time thanks
  6. I always do manual upgrades and follow the steps in the upgrade_instructions.pdf to make sure I don't mess up (even if I've done it several times before). In the pdf that comes with the 7277 build, it seems half the steps are missing, including perhaps the most important part of saving the config files. I followed the normal upgrade instructions from an older build as I assume 7277 was wrong. Did something change with regards to the upgrades or is the PDF wrong?
  7. My needs are very basic and I can live with loss of access to Passwordstate for a little while if my web/db server go down. I currently do daily backups of all my DBs via jobs in SQL and copy the .bak files to another location. If the worst were to happen and I lose my vm, can I simply reinstall the same version of Passwordstate on a new vm, restore the db and gain access to my passwords again? Or is the process more complicated/other considerations I'm not aware of? Thanks
  8. We're very basic users of password state. I do not use the automated backups (I handle SQL and passwordstate folder backups myself). I do not use any AD synchronization and when I add a new user, I click the "Add" button instead of the "Add from AD" button. I put the userid in the format of domain\username and everything seems to work just fine (and we don't get prompted to login, it goes works) Before I take the plunge and go from version 6 to 7, I was checking the forums to see if there were any issues and I came across this post: http://www.clickstudios.com.au/community/index.php/topic/139
  • Create New...