Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Admins cannot view encrypted field #11794

Closed
2 tasks done
CVogus opened this issue Sep 7, 2022 · 1 comment
Closed
2 tasks done

Admins cannot view encrypted field #11794

CVogus opened this issue Sep 7, 2022 · 1 comment
Assignees

Comments

@CVogus
Copy link

CVogus commented Sep 7, 2022

Debug mode

Describe the bug

Users with 'Admin' set as 'Grant' in either group or individual permissions are unable to view encrypted fields when viewing an asset. However, when the user with 'Admin' edits the asset, they are able to see the encrypted field information without an issue (this creates a lot more clicks to view information).

Also, it appears the encrypted field tooltip is broken for 'Admin' users (possibly broken as a result of info not displaying?)

When a user is set to 'Super Admin', the encrypted field is viewable while searching assets or viewing individual assets.

Edit: After further testing, it would appear any user with the ability to edit an asset can see the encrypted text. So this is not necessarily related to just admin privileges.

Reproduction steps

  1. As a user with 'Admin' search an asset.
  2. View an asset.
  3. Any encrypted fields display "ENCRYPTED" in place of information.

1.2 As a user with 'Admin' edit an asset.
2.2 Encrypted fields display unencrypted information.

Expected behavior

As a user with 'Admin' encrypted information should be viewable from all places that the UI displays encrypted fields, similar to the way it displays for 'Super Admin' users.

Screenshots

image

image

image

Snipe-IT Version

6.0.10 Build 8610

Operating System

Debian 10

Web Server

Apache2

PHP Version

PHP8.1

Operating System

Windows 11

Browser

Google Chrome

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

@welcome
Copy link

welcome bot commented Sep 7, 2022

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants