Password management

Yes it is completely planned, we only have to develop this feature. If anybody wants to get involved with such a feature, feel free!

Are there any special demands for your password management we need to know?

Good ideas, thanks! Any other feature request before we dive deeper in development?

It would be very nice to have some kind of one click login and also the possibility to save passwords after they are entered. But I guess this is going to be hard to implement without having a native application on the client. Would it be doable using some kind of browser extension?

The tool i am using at the moment is this one:

https://agilebits.com/onepassword

But it stores all passwords on every machine. Except for that it has all features I need. You have the possibility to save passwords after you entered them and the one click login is very reliable. You can store the passwords in folders. You can generate random passwords. You can tag the passwords.

What do you think of these features?

I would invest some time in this. But I need it quite fast. Would you help me define the steps to create a first version?

This is a first list of todos:

• Password content type
• Password categories taxonomy vocabulary
• Field encryption (http://drupal.org/project/field_encrypt http://drupal.org/project/encrypt)

The password content type has these fields:

• Title
• URL (Link)
• User (Text, encrypted)
• Password (Text, encrypted)
• Category (Term reference to Password categories)
• Customer (Entity reference to customers)

All of them except the title are optional.

Some optional features:

• Require the user to enter his password the first time he visits the password list and after 5 min of inactivity
• Field formatter to easily copy passwords (http://www.steamdev.com/zclip/)
• Generate password button
• One click login
• Storing passwords after entering them in the browser

There is an alternative to the field_encrypt module:

http://drupal.org/project/password_field

But i think from looking at the project page, field_encrypt is the better choice.

Is there a missing part in my first draft? What should be added?

Another thought: Should this even be part of ERPAL?

This could be an ERPAL feature. If it`s one, it's important, that we could add those password node types to projects, tasks, activities and documents, so that you'll have quick access to it.

Can you explain on which node types these fields should be?

We should reference a customer and/or a project from a Password. Actually it should have a customer and a project reference field.

But tasks, documents and activities should be referenced the other way around, right?

I suggest to start with a first new feature erpal_passwords and the ui feature erpal_passwords_ui

There we have a new content type erpal_password with fields described in http://drupal.org/node/1937588#comment-7317594

I think instead of the field

"Customer (Entity reference to customers)"

We should also allow referencing to projects and tasks.
We need a access control module that follows some rules:

- password is only visible if user is in general allowed to view passwords and if the password is referenced to a node the user has view access to.

This will not be part of the ERPAL distribution but available as a separate feauter, anybody can plug in.

Furthermore we need one view to show all passwords, filterable by fulltext search string (title field) and category terms.

After that we need a ui concept how to show passwords on projects and tasks (just the way we show files there). Important is, that these views are only part of this new feature and not part of other ERPAL modules.

I think instead of the field

"Customer (Entity reference to customers)"

We should also allow referencing to projects and tasks.
We need a access control module that follows some rules:

Can you please explain how the fields should look like? Should there be a field for each content type? Or one multi value field referencing all of them? Do you have something similar in ERPAL already?

Could you help me with the access thing later on?

I would suggest creating a third module for integration with ERPAL so the erpal_passwords and erpal_passwords_ui have no dependency to ERPAL. For example the reference field described above should not be part of the erpal_passwords module, right?

My suggested module names:

• passwords
• passwords_ui
• passwords_erpal

Can you please explain how the fields should look like? Should there be a field for each content type? Or one multi value field referencing all of them? Do you have something similar in ERPAL already?

It should be one field that allows referencing all of these types. We handle mail attachments this way but the ERPAL mail modul is under development.

Could you help me with the access thing later on?

Of course, we will use the aul module instead of acl to reduce the number of grants per user to avoid big queries that will slow down ERPAL a lot.

OK, we can split that in three features for general use.

I found another module to help us:

http://drupal.org/project/zeroclipboard

What other dependencies do we have? Should I just create the feature and the look into what dependencies are actually needed?

Yes I think thats the best way to go. Create the feature and check dependencies when exporting the feature.

Are there any updates here Lukas? I am going to postpone this one, because we are not actively working on this feature and need to wait for Lukas.