Hi everyone, I’m running into a limitation regarding Kratos → Polis/Jackson integration. It was described earlier in this thread. In my setup, I need Kratos to start the OIDC flow against Polis without requiring a separate OIDC provider configuration for every tenant/product combination. Encoding

tenant

and

product

in the

client_id

only works when the set of connections is fixed and predefined. I’m trying to support a multi-tenant environment where tenants and their Polis connections can be created dynamically, and Kratos should be able to select the appropriate

tenant

and

product

based on information sent by the client (for example during the login request). Without this capability, it appears that I would need to configure one OIDC provider in Kratos for every Polis connection, which doesn’t scale. My question is: Is it possible (or planned) for Kratos to support passing dynamic client_id to the OIDC, so that Kratos can fully integrate with Polis/Jackson in a dynamic multi-tenant scenario? If not, is there any recommended pattern for achieving this kind of dynamic resolution? Thanks for any guidance!

Hey @plain-horse-41561 at the moment I can't think of any way to work around this. Maybe @creamy-art-71586 has an idea or knows if this is something we would address at some point.

This is something we want to address in the future but currently I can't think of a workaround