fix(jans-config-api): user attributes not updated

[moabu]

When creating a new user and providing an array for the attribute CustomObjectClasses, the request is processed, however, after loading the newly created user, the attribute is empty.

[pujavs]

In LDAP DB the CustomObjectClasses is returned in response but not in My-SQL or Postgresql.
assigning to @yurem
LDAP-Screenshot:

MySQL-Screenshot:

[yurem]

It works as expected. Only LDAP ORM stores all provided OC because it's LDAP specific approach. In CB/Spanner/MySQL/PostgreSQL ORM uses only first OC to determine table name. I takes it from bean definition:

@DataEntry
@ObjectClass(value = "jansPerson")
public class User extends SimpleUser {

Why do you think we need to support storing OCs if DB not really need it?

[pujavs]

@moabu, request you to please provide your feedback on @yurem query.

[yurem]

Also, please update issue description to specify that the question is about CustomObjectClasses

[moabu]

I understand, but then it would be great if the backend would return an error, when the storage is not LDAP and custom OCs are provided.Now it suggests that all provided attributes were persisted, however, that one wasn't. This affects state management of the configuration ( which is saved externally outside the Jans deployment ) in our case Terraform. This would cause the Terraform state never to converge, as there would always be a delta between what Terraform believes the state of user should be (include the custom OCs) and what the backend reports is the state of the user (namely no OCs in case of MySQL DB).

Please note that you need to think about this in terms of the last applied state of the config. Having no clear response causes the integration to lose track of what actually happened as described above.