blocks|key|498656|text|我首先尝试了Everyauth，后来又使用了Passport。它给我的印象是更灵活一些，特别是。如果(例如)我需要为不同的提供者提供不同的逻辑。它还使(imo)更容易配置自定义身份验证策略。另一方面，它没有视图帮助器，如果这些对你很重要的话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|498657|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I tried out Everyauth first and have since gone to Passport. It struck me as somewhat more flexible, esp. if (for example) I need different logic for different providers. It also makes it easier (imo) to configure custom auth strategies. On the other hand, it doesn't have the view helpers, if those are important to you.

blocks|key|281975|text|请注意这篇文章的发表日期，它将表明这篇文章的相关性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|281976|根据我的经验，Everyauth的密码登录方式无法开箱即用。我正在使用express3，并且我像这样声明了我的中间件app.use(everyauth.middleware(app));，但它仍然没有将所有身份验证传递到我的模板中。上一次git提交是在一年前，我认为新的包已经破坏了所有的身份验证。现在我要试一下护照。|offset|length|style|CODE|281977|entityMap^0|0|1M|Z|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Note the date of this post, it will indicate how relevant this post is.

In my experience, Everyauth didn't work out of the box with it's password login style. I am using express3 and I declare my middleware like so <code>app.use(everyauth.middleware(app));</code> and it still wasn't passing in the everyauth local to my template. The last git commit was a year ago and I figure new packages have broken everyauth. Now I'm going to try passport.

blocks|key|498749|text|我过去经常使用Everyauth，更具体地说是使用mongoose-auth。我发现很难在不拆卸hard模块的情况下正确拆分我的文件。在我看来，Passport是一种创建登录帐户的更简洁的方法。我发现有一篇文章对http://rckbt.me/2012/03/transitioning-from-mongoose-auth-to-passport/很有帮助|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|498750|entityMap|0|LINK|mutability|MUTABLE|url|http://rckbt.me/2012/03/transitioning-from-mongoose-auth-to-passport/^0|2Y|1X|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I used to use Everyauth more specifically mongoose-auth. I found it hard to split up my files properly without dismantling the everyauth module. Passport in my opinion is a cleaner method for creating logins. There is a write up that I found very helpful <a href="http://rckbt.me/2012/03/transitioning-from-mongoose-auth-to-passport/" rel="nofollow">http://rckbt.me/2012/03/transitioning-from-mongoose-auth-to-passport/</a>

blocks|key|498825|text|这个回答有点晚了，但我找到了这个帖子(在听到所有关于Everyauth的负面反馈后)决定使用Passport……然后又讨厌它。它是不透明的，只能作为中间件工作(例如，您不能从GraphQL端点进行身份验证)，并且我遇到了多个难以调试的bug+(例如。How+do+I+have+two+Express+sessions?)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|498826|所以我去找了找https://github.com/jed/authom。对于我的需要，这是一个更好的库！它比其他两个库的级别要低一些，所以你必须自己做一些事情，比如把用户放入会话中……但这只有一行，所以真的没什么大不了的。|498827|更重要的是，它的设计为您提供了更多的控制，使您可以轻松地以您想要的方式而不是Passport预期的方式实现您的授权。此外，与Passport相比，它要简单得多，更容易学习。|498828|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/48777201/how-do-i-have-two-express-sessions/48777400#48777400|1|https://github.com/jed/authom^0|3H|Z|0|0|7|T|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

This answers a bit late, but I found this thread and (after hearing all of the negative feedback about Everyauth) decided to use Passport ... and then hated it. It was opaque, only worked as middleware (you couldn't authenticate from a GraphQL endpoint, for instance), and I hit more than one hard to debug bug (eg. <a href="https://stackoverflow.com/questions/48777201/how-do-i-have-two-express-sessions/48777400#48777400">How do I have two Express sessions?</a>).

So I went looking and found <a href="https://github.com/jed/authom" rel="nofollow noreferrer">https://github.com/jed/authom</a>. For my needs this is a much better library! It's a bit lower-level than the other two libraries, so you have to do things like putting the user into the session yourself ... but that's only one line so it's really no big deal.

More importantly its design gives you a lot more control, making it easy to implement your authorization the way you want and not the way Passport intended. Plus, compared to Passport it's a lot simpler and easier to learn.

<a href="https://github.com/bnoguchi/everyauth/" rel="noreferrer">Everyauth</a> and <a href="http://passportjs.org/" rel="noreferrer">Passport.js</a> seem to have very similar feature sets. What are some of the positive and negative comparisons between the two that would make me want to use one over the other?

Everyauth vs Passport.js?

身份验证

中间件

GraphQL

和似乎有非常相似的特性集。这两者之间的一些积极和消极的比较会让我想要使用一个而不是另一个？

问Everyauth vs Passport.js？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Everyauth vs Passport.js？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Everyauth vs Passport.js？
EN