User Authentication System in GO -

Is an already created user authentication system present in Go?

I'm coming from Ruby's background, and I really want to see something similar to the railways' which is a complete user management system, it takes care of everything to create a password to create it By making the form it also takes care of the database for data collection, installation of sessions and more.

I have found that there is a package which allows for social login (Facebook, Twitter ++) but it does not handle the storage user credentials with this email + password "normal "Does not even allow signup.

I may seem to go to this topic, there are some tutorials that have their origin, very unsafe, user login system.

I would really like to see a system that takes care of user ath and also allows for social login by Oath / Oath 2.

Background

Anything like this exists?

I am considering moving my rail app above a high performance structure because my current rail app is using too much RAM. Thus my eyes went out, however, without a solid user authentication system I can not change the bone is not a good practice to create my own user at system.

short answer: no.

Long answer: Ruby on the rail is a frame, go is a language. Creating a "universal" authentication system for Go will be a very big task and / or design by very to be opinionated because most of the systems relied on session collection and / or database. Tracks can do this (Divisions like Libs) because parts of the framework such as ActiveRecord and ActionController provide an abstract API that can talk to Devise.

For the most part, you will need to tie together what you want to get some libraries w / go

Some suggestions for libraries:

<

(password hashing)

(a micro-framework [Think: Sinatra-level] w /

(A feature wrapper for the standard database / sql package)

(a post form for the Go structure library)

Special to you Do not give user type, write your questions for you, etc. I am writing my "two user level" (regular versus administrator), server-side sessions, a single user table and a piece of HTTP middleware that "need the path "Wrap the routes and inspects the session, and it redirects users to a login page (and re-directs the current URL to direct