Skip to content

New UI Missing API #1778

@filipslezaklab

Description

@filipslezaklab

What's missing / is needed for 2.0 | is blocking UI development.

General

  • New endpoint for validating or getting reserved names for specific resource. Many resources like devices, locations, acl's etc. have constrains on names and when we will introduce paging for every endpoint it will be impossible to get that validation in current way that just loads all records of specific resource and just produce a map of reserved names on front end.
  • Pagination for every major resource, right now only Activity log endpoint have pagination, we need this for all major endpoints like locations overview, groups, ACL's or at least for those we expect to load for a prolonged time and have many records like users, groups and maybe network devices.
  • New endpoint/endpoints for getting minimal lists of options for given resource. This is needed for selection same issue as reserving names, could be combined but this should return a minimal list of records with identification and display value if possible so it can be used in filters, selections etc. without pulling whole resource with current get which pulls a lot of not needed data that slows down the request.

Overview

ACL's

  • New Destination concept that is separate from aliases

Enrollment

  • New enrollment page design requires new endpoints and new tables.

Licensing

  • Licensing info needs new endpoint or extended information in existing app info to account for new design needs.

Directory sync

  • We need a way to test external OIDC with optional directory sync validation before it's configured to account for the new validation step page in UI.

Wizard

New feature.

Settings

Todo - verify if current implementation doesn't workaround on current API for design's

External providers

  • Allow multiple OpenID providers
    • Add PUT
    • Add GET that returns multiple objects (list)
    • DELETE by ID, not name
  • Introduce Type enum, we already have specific configs for specific providers it will be easier for UI to display correct buttons if API returns what type it is for, right now it only guesses on URL. Enpoint auth_info.

Metadata

Metadata

Assignees

Labels

Type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions