Removing Lockdown-Accounts from import #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR attempts to remove the lockdown accounts from the evento import. Since it is technically difficult to remove the accounts from the Evento-API, they have to be removed on the ILIAS side of the import.
The API now adds an
isLockdownAccount-Field with a booleantrueorfalseset.I have made two commits for this PR:
The first one was to add the new API field to the importer and to delete the ILIAS-Evento Connection for the user account.
The second one is to deactivate the account entirely and remove it from HSLU-Roles. Without this commit, the account just stays as an LDAP-Account for a year till it expires.