We're trying integrating Ory Kratos and Ory Polis. Our plan was to configure Polis as a generic OIDC provider in Kratos. However, Polis's

/authorize

endpoint requires

tenant

and

product

query parameters to function, and Kratos's OIDC provider doesn't seem to support adding these custom parameters. Does this mean a direct Kratos-to-Polis OIDC integration is not a supported pattern? Is the recommended approach to use an application backend as an intermediary that calls the Kratos Admin API to create the session?

You can encode the tenant and product as clientId (‘tenant=tenantId&product=productId’) or use the clientId returned by the Polis connection

Thanks for clarification. But I would still need to add a separate kratos oidc for each polis connection?

That is correct

So that means that you can only use Kratos->Polis for a static set of connections? Polis looked very interesting because it will allow my customers to setup their connections via API. But that doesn’t work with Kratos because the OIDC connection is through configuration files.