I’m trying to figure out how to handle guest identities using Krakos.
By ‘guest identity’, I mean a unique, unshared identity, to allow users to use a service before committing to creating an account.
There are two use cases for this kind of flow:
- frictionless trial with upgrade to account, keeping data
- Guest checkout with the option to create an account afterwards
The way I’m imagining handling this with Kratos is using a custom server registration API that returns/stores an autogenerated identifier/password in the session. At this point, only the session owner can choose to upgrade the account (or an admin, in the case of customer support).
Using a custom server-side registration API means having to handle CSRF manually. Is there a better way to handle this?