As decided by the team for implementation, we will create a separate table to store the configuration for OIDC.

Reasons:

• only used in OIDC authentication
• creating a column in Proxy model will end up with it being 'NULL' most of the time
• no need of Operations doing the migration.
• can be extended later.

Technical specification:

• If nothing is saved in database, by default it is standard flow

• proxy has_one oidc_configuration

• On proxy creation, if OIDC is selected, create a record in this table. If the proxy already existed but does not have a corresponding record, on update create it as well.

• Table structure

  id	proxy_id	configuration	tenant_id
  PRIMARY KEY AUTO INCREMENT	BIGINT	TEXT	BIGINT

• configuration would be a serialized JSON

• create a trigger for tenant_id

Notes:

For now we decide to do it on proxy level, but in the future the OIDC configuration could belong directly to the application.