Encrypting OIDC secrets in static metadata

[Wessel, Keith]

In this case, though, it's not a prefix. It's a difference of the actual XML element:
<oidcmd:ClientSecret>verySecretClientSecretKeyValue1234567890</oidcmd:ClientSecret>

Versus

<oidcmd:ClientSecretKeyReference>secretReference1</oidcmd:ClientSecretKeyReference>

In the JSON, we have a "client_secret" key. Is there a different key or some other way of signaling that the value isa reference and not the actual secret vale?

Keith

-----Original Message-----
From: Cantor, Scott <cantor.2 at osu.edu> 
Sent: Wednesday, October 2, 2024 9:35 AM
To: Shib Users <users at shibboleth.net>
Cc: Wessel, Keith <kwessel at illinois.edu>
Subject: Re: Encrypting OIDC secrets in static metadata

> Is there a way to include a reference in static JSON-format
> metadata?

Should be the same, the XML just gets turned into the same façade as JSON, the same ClientInformation interfaces. It's the content of the field containing the secret that gets parsed out and checked fo the hash prefix.

I don't know the format so I don't know what the field is, probably just client_secret or something, whatever's in the spec.

-- Scott