blocks|key|4028455|text|护照|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4028456|模块化和transparent|4028457|good文档|unordered-list-item|4028458|
|4028459|社区贡献(由于它是与每个人和他们的狗(同样，由于它的模块性)|4028460|
)|4028461|每一次验证|4028462|4028463|开发历史悠久，发展成熟。|4028464|不再使用|4028465|的各种服务|4028466|4028467|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|11|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|14|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|P|3|Q|5|F|7|16|8|@]|9|@]|A|$]]|$1|R|3|S|5|F|7|17|8|@]|9|@]|A|$]]|$1|T|3|U|5|F|7|18|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

<h2>Passport</h2>

<ul>
<li>modular and transparent</li>
<li>good docs</li>
<li>community contributions (owing to it's modularity)</li>
<li>works with everyone and their dog (again, owing to it's modularity)</li>
</ul>

<h2>Everyauth</h2>

<ul>
<li>long development history, mature.</li>
<li>no longer maintained</li>
<li>great docs</li>
<li>works with a wide range of services </li>
</ul>

blocks|key|4028599|text|刚刚完成了从所有身份验证到护照的更改。原因如下。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4028600|4028601|Everyauth不够稳定。最后一根稻草是上周我被一个神秘的问题所困扰，在这个问题上，facebook身份验证可以在local.host和生产环境下工作，但在我在heroku上的测试环境中不能，即使有相同的代码和数据库和新的heroku应用程序实例。在这一点上，关于如何隔离这个问题，我已经没有理论了，所以删除所有身份验证是合乎逻辑的下一步。|ordered-list-item|4028602|提供了对使用用户名/密码凭据的标准身份验证的支持，但这种方式很难与单页面web应用程序方法集成。|4028603|我无法让所有身份验证都与谷歌帐户一起工作。|4028604|每一位作者的积极开发似乎都在下降。|4028605|4028606|移植令人惊讶地没有痛苦，只需要几个小时，包括手动测试。|4028607|所以很明显，我建议你去拿护照。|4028608|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|W|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|X|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

Just finished changing from everyauth to passport. The reasons were the following.

<ol>
<li>Everyauth is not stable enough. The final straw was last week I got bitten by a mysterious issue where facebook authentication would work on local.host and on the production environment, but not in my test environment on heroku, even with identical code and databases and a new heroku app instance. At that point I ran out of theories as to how to isolate the issue, so removing everyauth was the logical next step.</li>
<li>The way it provides support for standard authentication using username/password credentials is not easily integrated with a single page web app approach.</li>
<li>I was unable to get everyauth to work with Google accounts. </li>
<li>Active development of everyauth seems on the decline.</li>
</ol>

The port was surprisingly painless, only taking a few hours, including manual testing. 

So obviously, I recommend going for passport.

blocks|key|2301912|text|我首先尝试了Everyauth，后来又使用了Passport。它给我的印象是更灵活一些，特别是。如果(例如)我需要为不同的提供者提供不同的逻辑。它还使(imo)更容易配置自定义身份验证策略。另一方面，它没有视图帮助器，如果这些对你很重要的话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2301913|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|4028655|text|这个回答有点晚了，但我找到了这个帖子(在听到所有关于Everyauth的负面反馈后)决定使用Passport……然后又讨厌它。它是不透明的，只能作为中间件工作(例如，您不能从GraphQL端点进行身份验证)，并且我遇到了多个难以调试的bug+(例如。How+do+I+have+two+Express+sessions?)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4028656|所以我去找了找https://github.com/jed/authom。对于我的需要，这是一个更好的库！它比其他两个库的级别要低一些，所以你必须自己做一些事情，比如把用户放入会话中……但这只有一行，所以真的没什么大不了的。|4028657|更重要的是，它的设计为您提供了更多的控制，使您可以轻松地以您想要的方式而不是Passport预期的方式实现您的授权。此外，与Passport相比，它要简单得多，更容易学习。|4028658|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.

blocks|key|2302024|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|2302025|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|4028490|text|请注意这篇文章的发表日期，它将表明这篇文章的相关性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4028491|根据我的经验，Everyauth的密码登录方式无法开箱即用。我正在使用express3，并且我像这样声明了我的中间件app.use(everyauth.middleware(app));，但它仍然没有将所有身份验证传递到我的模板中。上一次git提交是在一年前，我认为新的包已经破坏了所有的身份验证。现在我要试一下护照。|offset|length|style|CODE|4028492|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.

<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?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

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

问Everyauth vs Passport.js？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Everyauth vs Passport.js？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Everyauth vs Passport.js？
EN