@accounts/meteor-adapter 中文文档教程
@accounts/meteor-adapter
MeteorJS 的 JSAccounts 适配器:使用 JSAccounts 身份验证覆盖和扩展 Meteor 方法和发布。
Installing
首先安装并添加到您的 Meteor 项目:
meteor npm install --save @accounts/meteor-adapter
Use in Meteor client-side
要与 Meteor 客户端一起使用,请使用您的 AccountsClient
实例和 Meteor
实例,并在您的 Meteor 客户端使用此包入口点(通常是 client/main.js
):
import { Meteor } from 'meteor/meteor';
import AccountsClient from '@accounts/client';
import { wrapMeteorClient } from '@accounts/meteor-adapter';
AccountsClient.config({}); // Config your accounts client
wrapMeteorClient(Meteor, AccountsClient);
现在,每次调用 Meteor.call
或 Meteor.subscribe
- JSAccounts accessToken
将附加到您的请求,您的服务器将能够验证它。
Use in Meteor server-side
要与 Meteor 客户端一起使用,请使用您的 AccountsServer
实例和 Meteor
实例,并在您的 Meteor 客户端入口点(通常是 server/main .js
):
import { Meteor } from 'meteor/meteor';
import AccountsServer from '@accounts/server';
import { wrapMeteorServer } from '@accounts/meteor-adapter';
AccountsServer.config({}); // Config your accounts server
wrapMeteorServer(Meteor, AccountsServer);
Meteor.startup(() => {
// ...
});
现在,每次调用 Meteor.methods
或 Meteor.publish
- JSAccounts accessToken
都会被解析和验证,并且 user
和 userId
将可在您的回调中使用,例如:
Meteor.publish('myPulication', function() {
const user = this.user(); // JSAccounts user, or null if there is no user at all
const userId = this.userId(); // JSAccounts user id, or null if there is no user at all
});
Meteor.methods({
myFunc: function() {
const user = this.user(); // JSAccounts user, or null if there is no user at all
const userId = this.userId(); // JSAccounts user id, or null if there is no user at all
}
});
请注意,如果在客户端调用没有经过身份验证的方法,< code>user 和 userId
将返回 null
值 - 所以您应该在您的方法中检查它。 如果用户指定了一个令牌但它无效 - 方法/发布将失败并出现 JSAccounts 错误。
@accounts/meteor-adapter
JSAccounts adapter for MeteorJS: override and extends Meteor methods and publication with JSAccounts authentication.
Installing
Start by installing and adding to your Meteor project:
meteor npm install --save @accounts/meteor-adapter
Use in Meteor client-side
To use with Meteor client-side, use your AccountsClient
instance and Meteor
instance, and use this package on your Meteor's client-side entry point (usually client/main.js
):
import { Meteor } from 'meteor/meteor';
import AccountsClient from '@accounts/client';
import { wrapMeteorClient } from '@accounts/meteor-adapter';
AccountsClient.config({}); // Config your accounts client
wrapMeteorClient(Meteor, AccountsClient);
Now, each time you call Meteor.call
or Meteor.subscribe
- the JSAccounts accessToken
will be appended to your request, and your server will be able to validate it.
Use in Meteor server-side
To use with Meteor client-side, use your AccountsServer
instance and Meteor
instance, and use this package on your Meteor's client-side entry point (usually server/main.js
):
import { Meteor } from 'meteor/meteor';
import AccountsServer from '@accounts/server';
import { wrapMeteorServer } from '@accounts/meteor-adapter';
AccountsServer.config({}); // Config your accounts server
wrapMeteorServer(Meteor, AccountsServer);
Meteor.startup(() => {
// ...
});
Now, each time you call Meteor.methods
or Meteor.publish
- the JSAccounts accessToken
will parsed and validated, and the user
and userId
will be available for use inside your callback, for example:
Meteor.publish('myPulication', function() {
const user = this.user(); // JSAccounts user, or null if there is no user at all
const userId = this.userId(); // JSAccounts user id, or null if there is no user at all
});
Meteor.methods({
myFunc: function() {
const user = this.user(); // JSAccounts user, or null if there is no user at all
const userId = this.userId(); // JSAccounts user id, or null if there is no user at all
}
});
Note that if there method is called without an authenticated use in the client side, the user
and userId
will return null
values - so you should check it inside your method. If the user specified a token but it's not valid - the method/pulication will fail with the JSAccounts error.