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

Better handling of changed ACTIVITYGROUPS #9

Commits on Dec 7, 2023

  1. Better handling of changed ACTIVITYGROUPS

    This patch improves the handling of changed activitygroups if the ACTIVITYGROUPS.AGR_NAME field will be used
    in the resource configuration.
    If you would implement the resource configuration with an association from the user to the activitygroup via the
    AGR_NAME field, midpoint will write down the whole attribute again when changing one entry in the list.
    Because the AGR_NAME field only stores AGR_NAMEs it has no information on the current from/to dates in the actual activitygroups
    field and will simply overwrite everything in the SAP with empty from/to fields. SAP generates the current date as a from date
    so if you have a role change on another date every role in the SAP will be deleted and added again. All the information
    about the actual date of assignment will be lost. This also generates a lot of audit entries in the SAP.
    
    To avoid this, this patch loads the current state of the user from the SAP and uses the existing data if nothing has
    provided by midpoint. To propagate actual changes in the ACTIVITYGROUPS from/to fields the change algorithm will check if
    the attributes from the midpoint are xml attributes. If yes it will simply use those values because they have the biggest
    accuracy. If not it will use the current data from the SAP for those values.
    Emil Militzer authored and iam-tk committed Dec 7, 2023
    Configuration menu
    Copy the full SHA
    5535694 View commit details
    Browse the repository at this point in the history