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

[FEATURE] Enable / Disable the Private Tenant through OpenSearch Dashboards Security Plugin #1317

Closed
Tracked by #1319
shanilpa opened this issue Feb 7, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request triaged ux / ui User Experience / Inferface related issues

Comments

@shanilpa
Copy link

shanilpa commented Feb 7, 2023

Context

Is your feature request related to a problem?
Currently the private tenant can only be enabled / disabled through YML configuration files. Configuring through these files is a complex and somewhat frustrating experience for admin users. In order to enhance the UX for configuring tenancy it would be nice to offer admin users a dynamic way to enable / disable the private tenant through OpenSearch Dashboards Security Plugin.

Other context notes

  • By default the private tenant is the default tenant for all users if not specifically configured by the admin.
  • Saved objects created in private tenants can not be accessed by other users.
  • Saved objects created in the global tenant are accessible to all users.
  • The global tenant can not be disabled

Users / Personas

  • Admin - This is a user that has access to the security plugin and can configure tenancy. They can also use tenancy like a non-admin user would.
  • Non-admin - These are users that do not have access to the security plugin, they can not configure tenancy but can use the feature if it is enabled and their admin has granted them appropriate permissions to do so.

What solution would you like?

NB: These are design mockups. Some copy is placeholder and not all interactions are polished.
Mockups may differ from the final launched feature.

1. Disable private tenant

  • Admin users can disable the private tenant if tenancy is enabled through the configure tab.
  • When the private tenant is disabled the default tenant for all users is set to the global tenant, however the user is able to change this to a custom tenant of their choosing.
  • Friction is introduced to notify the user and force them to consider their decision
Disable.Private.Tenant.mp4

2. Non-admin user notification

  • When the private tenant is disabled users working in a private tenant should be shown a persistent modal notifying them that the admin has disabled the private tenant
  • The non-admin user is prompted with a persistent modal that can not be cancelled out of.
  • After a set amount of time they are redirected to the global tenant

image

If users try to access a tenant via a url that has been disabled they will be notified that they no longer have access
image

When non-admin users try and switch a tenant they do not see the private tenant option
image

Additional Details

These UX improvements are based on work/tasks outlined in this issue and this RFC for making tenancy dynamically configurable.

@stephen-crawford
Copy link
Contributor

[Triage] Assigning to @shanilpa for further development. Thank you!

@kgcreative
Copy link
Member

@shanilpa - has this issue launched? If so, can we close it, referencing any merged PRs that resolve this?

see: opensearch-project/OpenSearch#5853

@shanilpa
Copy link
Author

This feature has launched: opensearch-project/security#2607

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triaged ux / ui User Experience / Inferface related issues
Projects
None yet
Development

No branches or pull requests

3 participants