feat: standardize how to add custom client claims (i.e. extend client schema)

[nynymike]

Just like there is a process for extending the schema of a person, organizations may need to add custom claims to the client object. Just a single example, let's say an organization has a business division code for distinct sets of clients, and wants to search to get a list of clients via the config api?

[yuriyz]

We have the way to extend Client attributes similar to User/Person mechanism. Following configuration allows custom attributes for client.

• dynamicRegistrationCustomObjectClass - specifies custom OC for client.
• dynamicRegistrationCustomAttributes - specifies custom attributes

...
 "dynamicRegistrationCustomObjectClass": "MyDynamicRegistrationCustomObject", 
 "dynamicRegistrationCustomAttributes": [
    "jansTrustedClnt",
    "myAttr1"
  ],
...

References (it's for gluu but same works in jans):

• https://gluu.org/docs/gluu-server/4.4/api-guide/openid-connect-api/#overview_2

[yuriyz]

@nynymike do we need to add something else or above is enough?

[yuriyz]

Client schema is extended via dynamicRegistrationCustomObjectClass and dynamicRegistrationCustomAttributes as described in comment above. @nynymike closing this ticket, please re-open if we need to change or improve our current approach.