Hi, We’re using Ory Network for authentication an...
# ory-network
b
Hi, We’re using Ory Network for authentication and have SSO configured for several providers (Microsoft, Google, GitHub). We recently added Swedish BankID as an OIDC provider. BankID does not supply an email address, so our identity schema requires the user to fill in their email after the OIDC flow completes (the missing-fields registration step). We use Ory Elements which handles rendering the “add email” field automatically. The problem: When a BankID user completes the QR scan and is redirected back to our app, they are correctly prompted to enter their email. However, when they submit the email, Ory re-initiates the BankID OIDC flow — requiring the user to scan the QR code a second time before registration completes. We confirmed this does not happen with GitHub (when we strip the email via Jsonnet), because GitHub’s re-authentication is seamless. With BankID, the re-initiation requires active user interaction (QR scan), making the UX broken. Questions: 1. Is there a way to prevent Ory from re-initiating the upstream OIDC flow when the user submits missing traits on the registration page? 2. Is there a supported mechanism to complete the OIDC registration without a second round-trip to the IDP when the only missing trait is email? We want to keep email as a required trait and use Ory’s built-in missing-fields flow — we just need to avoid the second IDP redirect. Thanks!
Seems related to this issue. Any plan to merge a fix? https://github.com/ory/kratos/issues/2863