Bug 55725 – UCS@school ID Connector: Add compatibility matrix Kelvin API

Bug 55725 - UCS@school ID Connector: Add compatibility matrix Kelvin API


Summary:	UCS@school ID Connector: Add compatibility matrix Kelvin API

Status:	NEW

Product:	UCS@school
Classification:	Unclassified
Component:	Documentation
Version:	UCS@school 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2023-02-20 11:08 CET by Nico Gulden
Modified:	2023-05-26 10:31 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Nico Gulden

2023-02-20 11:08:56 CET

The UCS@school ID Connector documentation should list the compatibility of its different versions to Kelvin API versions, preferred as a table, if suitable.

For example the first row lists the versions of the ID Connector. The first column lists the versions of the Kelvin API. And the crossing of the rows and the columns of the different versions receive a "OK", if they work together and are supported.

Comment 2 Daniel Tröder

2023-02-21 08:19:35 CET

The Kelvin plugin of the ID Connector uses the official Python Kelvin Client.
For that we have compatibility table: https://docs.software-univention.de/ucsschool-kelvin-rest-api/kelvin-client-compatibility.html
So from the knowledge of the used client version in the ID-C, we can deduce the minimum receiver-side Kelvin version.
That information can be used for the proposed table.

A problem for both compatibility tables: how do we keep them uptodate? The existing one is already missing a lot of versions...