Menu ▾ ▴

Different users - different views

Help
Frode Molstad
2008-12-01
2012-11-19

  • Frode Molstad

    Frode Molstad - 2008-12-01

    Hi,

    I have a hard time searching this forum. So I just add a new post related my issue.

    I want to use Keepass to manage the passwords related my customers and my employees. And I wanted the masterpassword to be maintained by one person. But every employee to manage the servers they work on.
    How is this best applied?
    I want the admins to be able to change passwords on the servers they manage, and only thouse passwords. So I want to set up one user with password for each of these. The passwords will be the same for meny of these users, but not all of the. And I want to remove all general logins, and use theyre emp.login.

    Any advice? I have tried looking for this in the Help section. But cant find anything.

    Plz advice!

     

    • Paul

      Paul - 2008-12-02

      Every employee will need to know the master password to unlock the database and are able to change it.

      I would use several databases if you need to limit users to particular groups of passwords.

      cheers, Paul

       

    • Rebecca Dolle

      Rebecca Dolle - 2009-01-06

      Hello Paul,

      I have the same need (multiple users, different security levels).

      How would the different databases work?
      Is there a way to have a config file to remember what entries to export?

      Thanks for your help!
      Becca

       

    • Paul

      Paul - 2009-01-06

      Becca, there is no way to automate this. I suggest you create folders in the master database, say Enterprise, Domain etc, and then export each of these folders to individual databases for your users.

      cheers, Paul

       

    • Luckyrat

      Luckyrat - 2009-01-08

      You might want to consider using field references. So you could have two sets of groups in the master database, one with the passwords themselves and one with the groups to be exported and distributed to users as Paul mentioned. The latter could be made up from entries that reference the passwords in the first group so that you only need to change the password in one place.

      Thanks,
      Chris

       

    • Paul

      Paul - 2009-01-11

      Chris, if you export an entry with a reference, does it take the referred field with it, or just have an entry with an invalid reference?

      cheers, Paul

       

      • Luckyrat

        Luckyrat - 2009-01-13

        Just an invalid reference.

        Sorry, I obviously misunderstood the purpose of the export feature. This is one example of somewhere that an option to actually export the value of the password could be useful. Whether it's enough on its own to justify the work to make it happen is up for debate I suppose.

        I can see the benefit of keeping the reference field intact (if you re-import to the same database in the future or import the source password at the same time) but my guess is that most people would expect to see their actual passwords in the export file by default.

        Anyone have a comment about adding that as a feature request?

        Thanks,
        Chris

         

    • Paul

      Paul - 2009-01-14

      Feature request!

      cheers, Paul

       

    • Luckyrat

      Luckyrat - 2009-01-19

      The feature request logged at the URL below could help lead to a solution to this need.

      https://sourceforge.net/tracker2/?func=detail&atid=609911&aid=2520757&group_id=95013

      Thanks,
      Chris

       

Log in to post a comment.

MongoDB Logo MongoDB