Custom attributes in oidc_client

[wacko-cornflower]

Hi,
I'm currently looking into the jans_oidc_client and defining them via the terraform provider. More specifically im looking into the custom attributes section in the documentation found here:
https://registry.terraform.io/providers/JanssenProject/jans/1.13.0/docs/resources/oidc_client#nested-schema-for-custom_attributes

Initial experimentation with trying to make use of this has shown unfruitful. Im wondering if I am at all using it as intended?

For instance creating a oidc_client with this custom attribute fails with some marshalling error:
The custom attribute:
custom_attributes { multi_valued = true name = "custom" values = ["ab"] }

The error:
Error: post request failed: could not marshal request: json: error calling MarshalJSON for type jans.CustomAttribute: invalid character 'b' in literal true (expecting 'r')

The use case is that i want to be able to make use of this custom attribute from within an update token interception script.

Any advice or pointers?

[nynymike]

Fredrik, Thanks for checking out Jans.

Both the Person and Client entities have attributes. I think this is referring to custom attributes for the Person Entity. Perhaps @moabu could shed some light on the implementation requirements for this custom_attributes configuration param with regard to the TF openid client.

If it is referring to Person entity attributes, as the email claim in the example would suggest, keep in mind that Jans has a process for extending Person schema--you may need to create columns in your RDBMS and also register the attribute for usage. See the Jans Docs: https://docs.jans.io/stable/janssen-server/config-guide/auth-server-config/attribute-configuration/ So if the attribute is not properly configured, I could see an error when you try to add it for release in the client configuration.

Also, I wonder if the name of that metadata should be released_custom_attributes or just released_claims ?

This question might be better moved to a Discussions thread, because it's not clear yet to me that it's a bug.