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

Restore "Secure Spaces" messaging #88368

Closed
azasypkin opened this issue Jan 14, 2021 · 1 comment · Fixed by #100448
Closed

Restore "Secure Spaces" messaging #88368

azasypkin opened this issue Jan 14, 2021 · 1 comment · Fixed by #100448
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Security/Spaces Platform Security - Spaces feature Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@azasypkin
Copy link
Member

Kibana version: 7.11.0

Describe the bug: in 7.11.0 we removed circular dependency between Spaces and Security plugins, but accidentally forgot to migrate "Secure Spaces" messaging functionality.

Expected behavior: Spaces management screens should offer user to secure Spaces with our security features.

Any additional context: To unblock our migration to dedicated TS projects we removed the remainders of this functionality in #88365. The change is made in a separate commit so it's easier to recover it later.

@azasypkin azasypkin added bug Fixes for quality problems that affect the customer experience Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! Feature:Security/Spaces Platform Security - Spaces feature labels Jan 14, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Security/Spaces Platform Security - Spaces feature Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants