You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Superlogin is a client & server library for integrating login and roles with access to CouchDB using secure sessions. It seems there is a lot of overlap with Hoodie with regard to managing client authenticate access to CouchDB data.
Hoodie seems to have much more mature client-side interface making offline client application design easier. Hoodie seems weak in integrating the application with server-side private API services which ideally would use the same session and user roles to access private services.
I would love to see these two worlds integrated. Has anyone from the Hoodie community taken a close look at Superlogin?
The text was updated successfully, but these errors were encountered:
I had a quick look at Superlogin and the biggest challange I see is that it’s built with express as far as I can tell, Hoodie is built with hapi.
We are also looking into adding providers now, ideally using our new plugin architecture. On the client side, we are thinking about an API like hoodie.signInWith(providername, options), see #75 (comment).
Let me know if you are still interested in Hoodie and 3rd party logins, happy to help you get involved in moving this forward
Superlogin is a client & server library for integrating login and roles with access to CouchDB using secure sessions. It seems there is a lot of overlap with Hoodie with regard to managing client authenticate access to CouchDB data.
Hoodie seems to have much more mature client-side interface making offline client application design easier. Hoodie seems weak in integrating the application with server-side private API services which ideally would use the same session and user roles to access private services.
I would love to see these two worlds integrated. Has anyone from the Hoodie community taken a close look at Superlogin?
The text was updated successfully, but these errors were encountered: