Kano can be used either with a local user account or embedded in others apps through an iframe. In this case, we provide the embedding app with a stateless token because authentication is managed by the embedding app with its own user accounts, this token allows the embedding app to use Kano just like if the user was also logged into. However, this token has usually no expiration date at all (or a long one) and no link with a user in the app DB. It seems that the JWT strategy allowed this in Feathers v3 but since Feathers v5 it appears that a JWT without a user ID does not work well in the default JWT strategy raising 404 error about user not found.
Kano can be used either with a local user account or embedded in others apps through an iframe. In this case, we provide the embedding app with a stateless token because authentication is managed by the embedding app with its own user accounts, this token allows the embedding app to use Kano just like if the user was also logged into. However, this token has usually no expiration date at all (or a long one) and no link with a user in the app DB. It seems that the JWT strategy allowed this in Feathers v3 but since Feathers v5 it appears that a JWT without a user ID does not work well in the default JWT strategy raising 404 error about user not found.
Related to https://github.com/kalisio/kdk/issues/699.