Bug 51662 – Kelvin API ignores deletion_grace_period settings

Bug 51662 - Kelvin API ignores deletion_grace_period settings


Summary:	Kelvin API ignores deletion_grace_period settings

Status:	NEW

Product:	UCS@school
Classification:	Unclassified
Component:	HTTP-API (Kelvin)
Version:	unspecified
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:	2020-07-11 05:51 CEST by Daniel Tröder
Modified:	2021-10-01 12:06 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.091
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Workaround is available
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 Daniel Tröder

2020-07-11 05:51:58 CEST

The Kelvin API does not honor the import settings for deletion_grace_period (and possibly others).
The technical reason is, that the code for handling user deletion (incl. the SiSoPi scenario) is in UserImport.do_delete() and not in ImportUser.remove().
The Kelvin API simply calls ImportUser.remove().

Comment 1 Daniel Tröder

2020-11-06 08:14:38 CET

As a workaround, the "ucsschoolPurgeTimestamp" UDM property can be set.
That is anyway more suitable for the use of a REST API.

To be able to set and retrieve the value of a UDM property, add it to "mapped_udm_properties" in the import configuration.

"ucsschoolPurgeTimestamp" values have the format "%Y-%m-%d".