nextcloud / nextcloud/passman

View Previously Shared Credentials

Open
#395 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature request
Dominant language
JavaScript
Stars
823
Forks
117
Avg merge
1d 21h
Merged PRs (30d)
8

Description

Feature request

User type: Logged-in

User level: Beginners, intermediate or advanced

Description

I have imported over 800 passwords from Lastpass and that is working well.

I think there is a needed feature here. I have many passwords which I am sharing with various staff members. If one of my staff members were to leave I need to quickly see which of my passwords were being shared with that person. I think all businesses that use this in a shared 'Team' environment as we are will run into a similar issue.

There appears to be no way for me to quickly see which of my passwords are shared ie; via a tag or category etc...

I have created a video so you could experience the significance of this problem more directly: https://www.youtube.com/watch?v=oJB5C5g2yV8

This is even while knowing exactly which 2 passwords shared. In reality, I would not know which were shared the process would be more difficult yet.

It seems a search for Shared would be of great value at a minimum. At a maximum, a search for Shared with Which User.

Benefit / value

Would protect the share owner by insuring at their earliest desire they could quickly disable shares associated with staff or other persons they felt presented a risk. Even in ordinary circumstances in cases where there are passwords that number in the hundreds, would provide more control to the share owners by allowing them to put on their radar shares they might not be be prone to knowing otherwise.

Risk / caveats
Sponsorship

Are you a developer willing to implement this feature?: no

Can you sponsor the development of this feature or do you know someone who can?: 50.00 contributor


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with issue #395 and inspect the passman application entry points for credential listing and sharing. Define how owners can find credentials shared with a specific user, then verify that the result supports quickly identifying and disabling those shares; the issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.