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

[newPlatform] [browserSide] Migrate Security #2701

Closed
6 tasks done
sortiz1191 opened this issue Dec 21, 2020 · 2 comments
Closed
6 tasks done

[newPlatform] [browserSide] Migrate Security #2701

sortiz1191 opened this issue Dec 21, 2020 · 2 comments
Assignees
Labels

Comments

@sortiz1191
Copy link
Contributor

sortiz1191 commented Dec 21, 2020

Parent issue #2660
Branch feature/2701-migrating-plugin-browser-side-security

Description

Migrate security

Tasks

  • Creating route for /security using React router at /public/app-router.tsx
  • Create security subroutes for users, policies, roles and role-mapping
  • Import Users component for Security tab
  • Import Roles component for Security tab
  • Import Policies component for Security tab
  • Import Roles mapping component for Security tab
@sortiz1191 sortiz1191 self-assigned this Dec 21, 2020
@sortiz1191
Copy link
Contributor Author

sortiz1191 commented Dec 23, 2020

-> Solve import problems from these files:

  • public/components/common/hooks/use-index-pattern.ts
  • public/components/common/hooks/use-filter-manager.ts
  • public/components/common/hooks/use-time-filter.ts

-> Add useHistory component for react router
-> Add useLocation component for check current URL and select current tab at security
-> Refactor getInternalUsers function: Now, if the security check is false, don't try to get Elastic users.
-> Change WzRequest import for these role files:

  • Create-rule.service.ts
  • delete-rules.service.ts
  • get-rules.service.ts
  • update-rule.service.ts

@Desvelao
Copy link
Member

This section was migrated to use the ReactJS router as part of this pull request: #6689.

So this issue can be closed.

@Desvelao Desvelao closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants