<p>I am trying to build my first web app in go, after ditching NodeJS. With node, there are tons of frameworks and tutorials for passport, so it was quite easy to get it running, but I am having trouble doing the same thing in go.</p>
<p>I need a basic email/password authentication system, and so far I've found <a href="https://github.com/go-authboss/authboss" rel="nofollow">authboss</a>, but that seems dormant, and a few guidelines on how to build your own session system (I know I shouldn't roll my own though). The most promising library so far I think is <a href="https://github.com/markbates/goth" rel="nofollow">goth</a> which seems active and offers Auth0 support, which I think would be great for my needs.</p>
<p>Do any of you have any experience with goth, are there any other simpler solutions? And also I like to learn instead of pasting code so a good walkthrough on how to use libraries are appreciated!</p>
<hr/>**评论：**<br/><br/>lumost: <pre><p>Plus one for goth, these days most customers prefer some level of external authentication. In the SaaD world this mesns SAML, for everyone else its usually login with google/facebook.</p>
<p>Auth0 gives you all that out of the box along with the nice to haves such as logging in as a customer etc. And goth makes it easy to use auth0.</p>
<p>Also worth noting thar if you're looking to build a webapp in go it may be worth checking out <a href="http://gobuffalo.io/docs/getting-started" rel="nofollow">http://gobuffalo.io/docs/getting-started</a> which is ny the same author as goth.</p></pre>drakonka: <pre><p>I am looking into goth right now and to using it in conjunction with Auth0. However, I am very new to both (and to Go in general); the impression I get is that goth is not suitable to my specific needs because it is specific to <em>web</em> client authentication, whereas the current interface to my go app is CLI (and that is also how I have set up my Auth0 client). The first issue I already ran into is the fact that goth requires a "callbackUrl" when registering a new provider, which it seems Auth0 requires for web clients but not CLI clients.</p>
<p>However, for web interfaces goth does come highly recommended. So what I am thinking is having authentication plugins for different interfaces - loading the web auth plugin which uses goth from the web interface (which I will later have), and writing my own Auth0 implementation for the cli interface. Not sure if this is at all a great solution yet, or if I've missed something and could/should be using goth for both after all; I'll just have to experiment.</p>
<p>Edit: typo</p></pre>
