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

[moabu]

When updating the organization, the organization title, as well as the DN/BaseDN are not updated.

[pujavs]

@moabu, dn and baseDn are internally generated and can be updated to only applicable schema values to avoid schema class violation and the config-api endpoints conforms to it. Same is applicable to dn and baseDn update for any schema object.

Video:
SMTP_dn_baseDN_Issue_2756.zip

Screenshots:

[moabu]

OK, understood about the Dn/BaseDn, however, I'm not always getting an error from the API when using an incorrect value. For example following request returns a 200 OK response:

[
	{"op":"add","path":"/dn","value":"ou=groups,o=jans"},
	{"op":"add","path":"/baseDn","value":"o=janssen"}
]

If the API doesn't return an error, it's hard to handle it properly on the provider side.

Also what about the OrganizationTitle? Should I be able to change that?

[pujavs]

on verifying the code found that we have organizationTitle only getter without any setter or corresponding attribute in model class.
@yuriyz request your advice.
https://github.com/JanssenProject/jans/blob/main/jans-auth-server/persistence-model/src/main/java/io/jans/as/persistence/model/GluuOrganization.java#L92

[yuriyz]

@pujavs removed this method in https://github.com/JanssenProject/jans/pull/2948/files

We don't need it, I removed it. There is already getter/setter for title.

[pujavs]

thankyou @yuriyz
cc @moabu

[moabu]

Ok I'll confirm and close the ticket if everything goes as expected . Thanks @yuriyz and @pujavs

[moabu]

Confirmed.