You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The security plugin allows internal users to be selected with a wildcard (*) when mapping roles to internal users, but Workspaces collaborators does not follow the same behavior.
To Reproduce
Workspace privacy is set to "private to collaborators"
Go to workspace collaborators page
Add a new user collaborator with a wild card in the ID i.e. "*_access_test"
Users with that suffix, i.e. "user_access_test" are unable to access the workspace.
Expected behavior
Any user with an ID matching the collaborator ID should be able to access that workspace.
This is inline with existing behavior in the security plugin, where Roles can be mapped to internal users with a wildcard, i.e. "*_access_test" will match any user with that suffix.
XL-Lewis
changed the title
[BUG] Wildcard behavior mismatch between user/group in workspace collaborator and security roles
[BUG] Wildcard behavior mismatch between user/group in workspace collaborator vs Security Plugin Roles
Mar 6, 2025
The security plugin allows internal users to be selected with a wildcard (*) when mapping roles to internal users, but Workspaces collaborators does not follow the same behavior.
To Reproduce
Expected behavior
Any user with an ID matching the collaborator ID should be able to access that workspace.
This is inline with existing behavior in the security plugin, where Roles can be mapped to internal users with a wildcard, i.e. "*_access_test" will match any user with that suffix.
OpenSearch Version
2.19.1
Dashboards Version
2.19.1
Plugins
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
The text was updated successfully, but these errors were encountered: