-
Notifications
You must be signed in to change notification settings - Fork 243
[WIP] Enable Access Control Management API & UI Page #376
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
Conversation
ui/src/api/api.tsx
Outdated
| }).then((response) => { | ||
| const reason = "Delete from management UI."; | ||
| return await Axios.post( | ||
| `${API_ENDPOINT}/users/${userrole.userName}/userroles/delete?code=${token}`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Move all tokens of access control management APIs into header with a common axios.create() function.
Please check if it's an acceptable way. If so, I will implement the practice to all APIs.
|
Would this only work for SQL based registry? Or for both purview & SQL based reigstry? |
In current implementation, this only work for SQL based Access Control with API layer. Also, I've tried to store access control records into Purview to simplify required resources. However, the concurrency control is still a big problem. If that's fixed, we can implement access control management into purview as well. |
|
Create a new PR for access control plugin experience: #409 |



What is covered:
get,add,deleteuser role records in SQL database and protected with "admin" role/management&role-managementrouter.What is NOT covered:
Init_rbac()Function and TODO are added. However, current API server & client still have gaps