[GH-ISSUE #80] Don't show Organization ciphers to unconfirmed users #41

New issue

Closed

opened 2026-03-03 01:24:05 +03:00 by kerem · 5 comments

kerem commented 2026-03-03 01:24:05 +03:00

Owner

Copy link

Originally created by @mprasil on GitHub (Jul 13, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/80

This leads to confusion and ciphers that can't be decrypted (#77)

Originally created by @mprasil on GitHub (Jul 13, 2018). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/80 This leads to confusion and ciphers that can't be decrypted (#77)

kerem 2026-03-03 01:24:05 +03:00

• closed this issue
• added the
  bug
  label

kerem commented 2026-03-03 01:24:06 +03:00

Author

Owner

Copy link

@mprasil commented on GitHub (Jul 13, 2018):

I've totally missed the 2f892cb commit. So chances are this might be resolved already. Going to rebuild the image and test.

<!-- gh-comment-id:404775076 --> @mprasil commented on GitHub (Jul 13, 2018): I've totally missed the 2f892cb commit. So chances are this might be resolved already. Going to rebuild the image and test.

kerem commented 2026-03-03 01:24:06 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Jul 13, 2018):

It's a partial fix, at least. This hides the ciphers, but we should probably also not show the organization or the collections unless the user is confirmed.

We should also make sure that an unconfirmed admin or owner can't make changes to the org.

<!-- gh-comment-id:404775413 --> @dani-garcia commented on GitHub (Jul 13, 2018): It's a partial fix, at least. This hides the ciphers, but we should probably also not show the organization or the collections unless the user is confirmed. We should also make sure that an unconfirmed admin or owner can't make changes to the org.

kerem commented 2026-03-03 01:24:06 +03:00

Author

Owner

Copy link

@mprasil commented on GitHub (Jul 13, 2018):

Good point do you want to keep the issue open for that?

<!-- gh-comment-id:404777402 --> @mprasil commented on GitHub (Jul 13, 2018): Good point do you want to keep the issue open for that?

kerem commented 2026-03-03 01:24:06 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Jul 13, 2018):

Yeah, I think we should leave it open for now.

<!-- gh-comment-id:404781315 --> @dani-garcia commented on GitHub (Jul 13, 2018): Yeah, I think we should leave it open for now.

kerem commented 2026-03-03 01:24:06 +03:00

Author

Owner

Copy link

@mprasil commented on GitHub (Jul 17, 2018):

This should be completely resolved with #89 merged in.

<!-- gh-comment-id:405527843 --> @mprasil commented on GitHub (Jul 17, 2018): This should be completely resolved with #89 merged in.

kerem referenced this issue 2026-03-03 02:19:55 +03:00

[PR #41] [MERGED] Use proper toolchain in Dockerfile #2590

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels   

SSO

  

Third party

  

better for forum

  

bug

  

bug

  

documentation

  

duplicate

  

enhancement

  

future Vault

  

future Vault

  

future Vault

  

good first issue

  

help wanted

  

low priority

  

notes

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

troubleshooting

  

wontfix

No labels

SSO

Third party

better for forum

bug

bug

documentation

duplicate

enhancement

future Vault

future Vault

future Vault

good first issue

help wanted

low priority

notes

pull-request

question

troubleshooting

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/vaultwarden#41

No description provided.