Appwrite调用account.get()报错：Guest角色缺少account权限求助

实现注册与登录接口时，调用account.get()抛出AppwriteException：User (role: guest) missing scope (account), not able to get account after creating a session，已困扰3天。尝试查阅Appwrite文档修改Guest角色权限，但未找到account.get()相关设置，本地部署Appwrite后问题仍未解决。

注册账户控制器代码 #

const User = require('../model/User');
const { Client, Account } = require('appwrite');

exports.register = async (req, res) => {
    try {
        const { name, email, password } = req.body;

        // Validate data if exist
        if (!(name && email && password)) {
            return res.status(401).json({
                success: false,
                message: "All fields are required"
            })
        }

        // Check user already exist or not
        const doesExist = await User.findOne({ email })
        if (doesExist) {
            return res.status(401).json({
                success: false,
                message: "User already exists"
            })
        }

        //check if email is in correct format
        if (!(validateEmail(email))) {
            return res.status(401).json({
                success: false,
                message: "Invalid Email"
            })
        }

        // Save to DB
        const user = await User.create({
            name,
            email,
        })

        user.password = undefined

        const client = new Client()
            .setEndpoint('http://localhost/v1')
            .setProject(`${process.env.APPWRITE_PROJECT_ID}`);
        ;

        const account = new Account(client);

        await account.create(
            user._id.toString(),
            email,
            password,
            name
        );

        await account.get()

        return res.status(200).json({
            success: true,
            user,
        })

    } catch (error) {
        console.log(`Error :: register route :: ${error}`);
        return res.status(500).json({
            success: false,
            message: error.message
        })
    }
}

function validateEmail(email) {
    var re = /\S+@\S+\.\S+/;
    return re.test(email);
}

登录账户控制器代码 #

const User = require('../model/User');
const { Client, Account } = require('appwrite');

exports.login = async (req, res) => {
    try {
        const { email, password } = req.body;

        // Validate data
        if (!(email && password)) {
            res.status(401).send('All fields are required')
        }

        // check if user exist
        const user = await User.findOne({ email })

        // if user does not exist
        if (!user) {
            return res.status(401).json({
                success: false,
                message: "User does not exist"
            })
        }

        const client = new Client()
            .setEndpoint('http://localhost/v1')
            .setProject(`${process.env.APPWRITE_PROJECT_ID}`);
        ;

        const account = new Account(client);


        await account.createEmailSession(
            email,
            password,
        );

        await account.get()


        return res.status(200).json({
            success: true,
            user,
        })


    } catch (error) {
        console.log(`Error :: login route :: ${error}`);
        return res.status(500).json({
            success: false,
            message: error.message
        })
    }
}

问题原因与解决方案 #

核心原因 #

Appwrite的Account.get()需要已认证的会话才能调用，仅创建用户或创建会话后，SDK的Client实例并未自动持有有效会话凭证，所以请求时仍以Guest角色访问，触发权限异常。

注册接口修复 #

注册用户后，需要主动创建登录会话，让Client获取认证凭证：

// 在account.create()后添加会话创建代码
await account.create(
    user._id.toString(),
    email,
    password,
    name
);

// 创建邮箱会话，获取认证凭证
await account.createEmailSession(email, password);

// 现在可正常调用account.get()
const appwriteUser = await account.get();

登录接口修复 #

创建会话后，需要确保Client持有有效认证信息，可通过获取JWT令牌并设置到Client：

// 创建会话后获取JWT
const session = await account.createEmailSession(email, password);
const jwt = await account.createJWT();

// 将JWT设置到Client，确保后续请求携带认证信息
client.setJWT(jwt.jwt);

// 调用account.get()
const appwriteUser = await account.get();

额外建议 #

• 无需在本地数据库重复存储用户基础信息，Appwrite的Account服务已提供完整用户管理能力，仅在需要扩展业务字段时，再存储关联的用户ID即可。
• 服务器端使用Appwrite SDK时，每次请求都是无状态的，需手动管理会话凭证；若为前后端分离场景，建议让前端保存会话Cookie或Token，后续请求携带凭证直接与Appwrite交互，减少服务器端代理逻辑。

内容的提问来源于stack exchange，提问作者Kshitij Ingale