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

feat (jans-config-api) : admin-ui apis refactoring #2388

Closed
duttarnab opened this issue Sep 15, 2022 · 0 comments · Fixed by #2390
Closed

feat (jans-config-api) : admin-ui apis refactoring #2388

duttarnab opened this issue Sep 15, 2022 · 0 comments · Fixed by #2390
Assignees
Labels
comp-jans-config-api Component affected by issue or PR enhancement kind-feature Issue or PR is a new feature request

Comments

@duttarnab
Copy link
Contributor

duttarnab commented Sep 15, 2022

Based on : Admin UI apis suggestion in #2227

AdminPermission

  • should naming be AdminPermission, AdminUIPermission, AdminUIUserPermission?
  • no get for individual permission, only possible to get all permissions at once. At the same time permissions can be individually updated or deleted.
  • which attribute should be the ID? permission?
  • ideally delete should only take the ID of the entity, e.g. permission

AdminRole

  • same concerns as for AdminPermission

AdminRolePermissionMapping

  • same concerns as for AdminPermission

AdminUI permission

  • API is missing attribute defaultPermissionInToken
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-jans-config-api Component affected by issue or PR enhancement kind-feature Issue or PR is a new feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants