Curious - in the

createUser

mutation, why are both the

email

and

password

nested inside another

email

object? https://www.graph.cool/docs/reference/simple-api/user-authentication-eixu9osueb/

Yes

So, does this mean that I can reference different types of authentication for the same user?

This is not the case; with the current authentication system, a user node can only be connected to one auth provider at the same time. it's the auth provider that was chosen when using

createUser

. It cannot be changed later.

I was thinking about the authenticate by secret, which works for all existing users, regardless of auth scheme

in the near future, all authentication providers will work similar to the anonymous auth provider.