Directory extension support

[NemoVDEynde]

Added support for entra directory extensions. The extensions need to be declared in the config separated by ";", only provide the actual names as "extension_{client_id}" prefix will be automatically added.

[matusmacik]

I would really not want to specify this as a general assumption for all extension attributes. I'm no expert in MS Entra, but looking at this topic, it seems that there are also other supported data types than "String". Also, they can be creatable, rather than just updatable (and other flags like multiplicity can play a role as well).

[matusmacik]

Please do not update the "versioning" of the connector.

[matusmacik]

Thank you for your contribution. This feature could certainly be interesting in the Entra connector, yet the implementation limits it to only the "User" object class (which could be potentially documented as a limitation). The more problematic part is the general assumption, which I pointed out in the following comment. In this case, more information about the attribute schema might be needed. We do not have a way to specify complex parameters in the configuration (yet), so the possibilities might be a naming convention or a path to a file containing the schema in a machine-readable format (which could be parsed by the connector).

[NemoVDEynde]

Thank you for your contribution. This feature could certainly be interesting in the Entra connector, yet the implementation limits it to only the "User" object class (which could be potentially documented as a limitation). The more problematic part is the general assumption, which I pointed out in the following comment. In this case, more information about the attribute schema might be needed. We do not have a way to specify complex parameters in the configuration (yet), so the possibilities might be a naming convention or a path to a file containing the schema in a machine-readable format (which could be parsed by the connector).

Hi thanks for your feedback, this is a feature needed by a project I am doing which I thought others might find useful as well. I am working on the feedback you have given, and am adding support for all different types. This documentation page states the following types:

• Binary - Attribute contains binary data.
• Boolean - Attribute contains a True or False value.
• DateTime - Attribute contains a date string.
• Integer - Attribute contains an integer.
• Reference - Attribute contains an ID that references a value stored in another table in the target application.
• String - Attribute contains a text string.
  These are pretty self explanatory except for the Binary one, i am not quite sure as to which type in java to use. Is midpoint able to handle binary values in some way? Or should I pass them as String?

[matusmacik]

Thank you, that sounds great! For the binary types, an "array of bytes" as for the "type" definition should be used. Here is an example in the case of the "photo" attribute.

[NemoVDEynde]

Hi
I have expanded the functionality for directory extensions to support multiple types single and multi value. I have also added a mandatory flag as the entra schema definition supports it.
Config is now done in a multivalued element with formatted text "Extension_{appId}_name;type;multivalued;required". The app Id has been added because it's possible to access attributes from different apps. the extension prefix is not required the connector will check for it. Multivalued and and required just need true/false.