Next-gen identity server replacing your Auth0, Okta, Firebase with hardened security and PassKeys, SMS, OIDC, Social Sign In, MFA, FIDO, TOTP and OTP, WebAuthn, passwordless and much more. Golang, headless, API-first. Available as a worry-free SaaS with the fairest pricing on the market!
if you create an account with passwordless, the config is completely messed up (first screenshot)
but if you first create an account with password then the passwordless config, it works fine (just brackets {})
Reproducing the bug
We updated Kratos to v1.1.0 then ran kratos migrate sql -e --yes url...
For some reason sign in with code (passwordless, magic codes) is working fine for new users but for existing users instead of creating config correctly (just {}) it creates something like {"address_type":"","used_at":{"Time":"0001-01-01T00:00:00Z","Valid":false}} but most importantly it replaces the current method (password/SSO) with just passwordless
here the SSO getting replaced by code (check the created_at, 8 min later)
Relevant log output
No response
Relevant configuration
No response
Version
1.1.0
On which operating system are you observing this issue?
None
In which environment are you deploying?
Kubernetes
Additional Context
I first contacted on Slack about this 3 months ago, no response.
Preflight checklist
Ory Network Project
No response
Describe the bug
if you create an account with passwordless, the config is completely messed up (first screenshot) but if you first create an account with password then the passwordless config, it works fine (just brackets {})
Reproducing the bug
We updated Kratos to v1.1.0 then ran kratos migrate sql -e --yes url...
For some reason sign in with code (passwordless, magic codes) is working fine for new users but for existing users instead of creating config correctly (just
{}
) it creates something like{"address_type":"","used_at":{"Time":"0001-01-01T00:00:00Z","Valid":false}}
but most importantly it replaces the current method (password/SSO) with just passwordlesshere the SSO getting replaced by code (check the created_at, 8 min later)
Relevant log output
No response
Relevant configuration
No response
Version
1.1.0
On which operating system are you observing this issue?
None
In which environment are you deploying?
Kubernetes
Additional Context
I first contacted on Slack about this 3 months ago, no response.