Hi,
With the offline discussions we had we have decided to introduce a new
table to store JWT audiences and any OIDC related properties which will be
introduced in future. The table has the following structure.
Table: IDP_OIDC_PROPERTY
Columns:
IDint(11) AI PK
TENANT_IDint(11)
I think its something related to OAuth only. So saving in SP properties
table isn't the most correct solution. AFAIR for the SAML case we have
saved properties separately with the registry resource. But rather than
saving this in registry +1 to save in DB.
And +1 for Option 2. But beware about the
Hi,
Currently new audience values to JWT id_tokens should be added via
identity.xml file and server needs to be restarted. With this approach we
cannot control the id_token audience at SP level since it gets applied
globally through identity.xml based configuration. In this case, we are not
able
