next apollo auth
1.0.0
此示例显示了如何使用Next.js和Apollo GraphQl实现身份验证。
├── components
│ └── forms
│ ├── login.js
│ └── signup.js
├── lib
│ ├── initApollo.js
│ └── withData.js
├── pages
│ ├── index.js
│ ├── login.js
│ └── signup.js
└── server
├── data
│ ├── resolvers.js
│ └── schema.js
├── models
│ └── User.js
├── services
│ └── passport.js
└── index.js在这里,我们有一个带有三个字段的User类型(电子邮件,全名和密码),一个带有配置文件字段的Query类型,只是为了使GraphQl的嘴保持在定义的查询类型时。我们有两种Mutation类型(登录和注册)。
type User {
email: String
fullname: String
password: String
}
type Query {
profile : User
}
type Mutation {
createUser ( email : String ! , fullname : String , password : String ! ) : User
login ( email : String ! , password : String ! ) : User
} 我们在这里关心的解析器是createUser和login 。他们都将email和password作为createUser参数,以额外的fullname参数为例。
Mutation: {
createUser ( root , { email , fullname , password } , { login } ) {
const user = new User ( { email , fullname } )
return new Promise ( ( resolve , reject ) => {
return User . register ( user , password , err => {
if ( err ) {
reject ( err )
} else {
login ( user , ( ) => resolve ( user ) )
}
} )
} )
} ,
login ( root , { email , password } , { login } ) {
return new Promise ( ( resolve , reject ) => {
return User . authenticate ( ) ( email , password , ( err , user ) => {
// user returns false if username / email incorrect
if ( user ) {
login ( user , ( ) => resolve ( user ) )
} else {
reject ( 'Email / Password Incorrect' )
}
} )
} )
}
}哎呀!我们只有一个模型(用户)。它接受电子邮件,用express-validator验证电子邮件。然后,我们有一个插件来告诉passport-local-mongoose将我们的电子邮件字段用作默认usernameField名。
const userSchema = new Schema ( {
email : {
type : String ,
unique : true ,
lowercase : true ,
trim : true ,
validate : {
isAsync : true ,
validator : ( v , cb ) =>
cb ( validator . isEmail ( v ) , ` ${ v } is not a valid email address` )
} ,
required : 'Please Supply an email address'
} ,
fullname : String
} )
userSchema . plugin ( passportLocalMongoose , {
usernameField : 'email' ,
errorMessages : {
UserExistsError : 'Email Already Exists'
}
} )麻省理工学院