[PB-37706] Role-Based Access Control is not reflecting in a condition in the browser extension

[iamfasal]

##IMPORTANT: PLEASE READ

Only use github issues for bugs.

We will be more than happy to help you on the community forum for:

• feature requests: https://community.passbolt.com/c/backlog
• issues related to an installation: https://community.passbolt.com/c/installation-issues
• general questions: https://community.passbolt.com/c/uncategorized

This is only a issue tracker for bugs related to the Passbolt Browser Extensions.
For passbolt API, docker, command line interface, in short any other bugs
please use the other relevant repositories.

If you are certain this is a new Browser Extension bug please use the following format:

ISSUE NAME

• Passbolt Version: Server 4.10.1 || Extension: 4.10.2
• Platform and Target:
  -- Browser: Chrome
  -- Web server: Docker

What you did

My normal users have restricted access using "Role-Based Access Control" which prevents them from previewing/copying passwords. However, when I login using the Chrome extension > Groups > MyGroup > Selected a listed password list > It allows both viewing and copying password even when the user is limited.

If we go in this below route first upon login, then it all works perfectly:
Login using the Chrome extension > Filters > Shared with me (The password was shared by admin) > Selected the password > It is not allowing viewing or copying password as expected.

If we go to Groups section upon login, it is not working as expected.

What happened

A way of navigation is not working as expected

What you expected to happen

If we restricted something for a normal user, it should reflect correctly everywhere. If we navigate via Groups first upon login, then it is not working as expected.

Any assistance/help would be appreciated.

[iamfasal]

Any update on this bug?

[Benj1er]

Hello @iamfasal,

Sorry for my late reply.

Thanks for your report.
A follow-up ticket was created on the internal tracker: PB-37706

Best regards

[iamfasal]

@Benj1er Any update on this ticket?

[Benj1er]

Hello @iamfasal,

The fix has been implemented, and will be available after the next release.
I'll let you know when it's done.

Best regards