[ANN] LoopBack API framework adds support for social login and account linking

[Raymond Feng]

We’re excited to announce that the LoopBack API framework now supports:

• Third-party login, to enable your LoopBack apps to allow login using existing accounts on Facebook, Google, Twitter, or Github.
• Integration with enterprise security services so that users can login with them instead of username and password-based authentication.
• Account linking to link an account authorized through one of the above services with a LoopBack application user record.  This enables you to manage and control your own user account records while still integrating with third-party services.

See http://strongloop.com/strongblog/authenticate-loopback-google-facebook-github/ for more details.

[Will Hoover]

Are there any plans in the near future for ArangoDB connector support?

--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/54fe0a30-5edc-4bbc-8a35-78eb5bce0da4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sanjay M]

On Tuesday, June 3, 2014 6:18:13 PM UTC+1, Raymond Feng wrote:
> We’re excited to announce that the LoopBack API framework now supports:
>

> Third-party login, to enable your LoopBack apps to allow login using existing accounts on Facebook, Google, Twitter, or Github.Integration with enterprise security services so that users can login with them instead of username and password-based authentication.Account linking to link an account authorized through one of the above services with a LoopBack application user record.  This enables you to manage and control your own user account records while still integrating with third-party services.

> See http://strongloop.com/strongblog/authenticate-loopback-google-facebook-github/ for more details.

Hi Raymond ,

Any idea when the API gateway with reverse proxy features will be available ?
Regards
Sanjay

[altsang]

Will, there's a jugglingdb adapter for ArangoDB, it should be trivial to wrap that up into a LoopBack connector.  We can definitely add this to the roadmap but whether its near term versus longer is subject to resources.  Do you want to sync up to see what your project and requirements are?

[altsang]

Sanjay,

The API gateway is being worked on in bits and pieces starting with client use cases that we're directing piloting with our customers.  There are component features to this gateway and we're in the midst of prioritizing those based on demand and at the same time we're laying foundation elements.   I don't have a concrete release date but if there's a need that you'd like to discuss with us definitely ping me back - @altsang

[Sanjay M]

Hi altsang,

Thanks for the reply.

I am looking at the use case wherein for API calls for example , all routes with /mycustompath is redirected to another API server(for example another service written in drip wizard ).

I read from Richard's recent post that you the the http proxy module under development . Can I download and test it?

[altsang]

Hey Sanjay PM at al AT strongloop.com, thanks!

[Will Hoover]

Currently we are evaluating possible Node.js stacks for various applications in a multi-location not-for-profit hospital environment with 4k+ total employees. So, judging by your statement we can expect to see an ArangoDB connector in the near future? Is there currently a feature request for this (I'd like to track the progress)?

 

I also have a few other questions to clarify StrongLoop's community policy:

I noticed that the Oracle and MSSQL connectors have a different licenses applied to them that requires a service agreement (versus other connectors like MySQL). Is this correct?

Are there plans to merge loopback-datasource-juggler and friends back into JugglingDB at some point?

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/755b9549-0b3d-49f3-a36f-95b895433eb7%40googlegroups.com.

[altsang]

Hey Will,  our roadmap for LoopBack is being driven by the combination of our paying customers, highly qualified prospects and the community at large.  Because we’re a commercial  startup, we obviously are making tradeoffs in the form of juggling priorities.  ArangoDB hasn’t come up among our customers and prospects before but I’m more than happy to get it on our roadmap.  To get a better sense of prioritizing it, it would be great if we can chat with you on your project that you’ve described above.  Would you be open to chatting with me?  You can reach me at al “@” strongloop.com

Regarding our policy on community versus commercial usage of our products.  LoopBack is a framework and it’s core function is fully open source and dual licensed for both folks who want to use and support it on their own as well as those who seek commercial support from our company.  There are extensions to LoopBack which we don’t consider community that are intended for commercial usage that are licensed under our StrongLoop license for production usage.  When you become a licensed subscriber, you’re allowed to use these extensions in production based on your application’s size and processing needs, and you also receive customer support and continued maintenance of these extensions.

In general our approach is to contribute enhancements to projects we depend on or work with when the enhancement would benefit the project. You can see this with our work on Node Inspector, Reggie, node-foreman, a bunch of other modules and Node core. We’ve made quite a few changes to JugglingDB to abstract out key components and do general clean up and we’re working on some scalability elements coming in the future. Going forward we’ll do our best to continue maintaining relative compatibility between the two.