fix(jans-config-api): problems with handling custom attributes

[moabu]

Custom attributes currently cannot be handled properly, as they can have any value type (string, number, boolean, or an array thereof). Since most upstream clients can only support fixed primitive types, the type of an attribute must be well defined.

[pujavs]

@yurem, request you to please suggest how to handle this request.

[yurem]

@pujavs Is this issue related to LDAP ORM only?

[yurem]

Here is result with LDAP ORM after update:

Now LDAP ORM uses schema to determine if attribute has integer/boolean/date type to convert value to corresponding java data type from string.

[moabu]

@yurem it was a general observation. I was using MySQL when I was investigating. We generally need the type of attributes to be well defined

[yurem]

Can you provide real example to reproduce this issue?

[yurem]

Same example which I run with MySQL DB:

[yurem]

I've checked ORM + PostgreSQL/Spanner/CB.
According to my testing ORM with LDAP/CB/Spanner/MySQL/PostgreSQL correctly store/return values with next types: Boolean/Integer(Long)/Date. Multivalued attributes we store:

1. As generic attributes in LDAP
2. As JSON in MySQL/PostgreSQL
3. As array in Spanner/CB.

[moabu]

This can be closed as resolved