Controlling post-authn flows for OIDC clients

[Wessel, Keith]

All,

I've got an OIDC client operating against my IdP that I need to opt out of attribute release consent. It seems like my options for doing this are:

1. Add a specific override to relying-party.xml to change the post-authentication flows for this client
2. Move the client from the JSON metadata I have now to the new SAML format, then leverage the existing entity attributes I have in place for controlling whether or not to prompt for consent.

Is there any other way to add any type of entity attribute to an OIDC client in memory? I know it can't be done in the json structure.

If not, is there any other way to control whether the consent flow fires for this client besides the ones I mentioned above?

Thanks,
Keith