Implement StormpathUser.login() Method

[rdegges]

This method needs to be implemented so that a StormpathUser model can be generated given a username / password pair.

See: https://github.com/strongloop/loopback/blob/master/common/models/user.js#L164 for reference.

[adriatic]

Happy to see that you came to the same place I just wanted you to look at :-) Based on the name of this issue I would assume the following will hold true:

1. You want to build the StormpathUser object that will exist as the alternative for LoopBack user object, exposing the same set of methods with the same profile (list of arguments). The implementation of _these new methods_ will of course be using relevant Stormpath API.
2. The LoopBack user will simply make changes described in the README.md file and (assuming that the application already exists) do a global replace of user with stormpathUser.
3. Then there is the whole set of Stormpath API, "components" (prebuilt UI object), templates that LoopBack does not have, so StormpathUser object can offer all these, with the caveat once a LoopBack user (human, developer) goes any deeper that the layer that is API-wise equivalent between Stormpath and LoopBack, there is no return back to LoopBack authentication services.
4. I am a lot more ambitious that I expect an average LoopBack user would be as I plan to create a _smaller scale equivalent_ of the Stormpath admin interface as a part of my app:

• https://api.stormpath.com/ui2/index.html#/applications
• https://api.stormpath.com/ui2/index.html#/directories
• https://api.stormpath.com/ui2/index.html#/groups
• https://api.stormpath.com/ui2/index.html#/accounts

as I do not want to wait until the admin section would be hosted by the user. So, I would like to see your thoughts about the evolution of this loopback-stormpath interface layer.

[arealmaas]

ohh, where is this in the pipeline? Really need this fixed soon.

[adriatic]

@AlmaasAre - you are watching this project in its earliest possible state, so there is nothing to be fixed, but a lot to be added :-)

[arealmaas]

@adriatic Ah, okey. That's what i feared :) But will manage to implement something of my own.

[jmls]

was anything ever done on this ? Or is this library dead in the water ?

[adriatic]

Dead as a door nail (lack of resources)

[jmls]

bugger. :(

[adriatic]

The term "lack of resources" is always related to "amount of interest". The frequency and amount of data in this issue are a good indicator of "amount of interest"

I am planning to revive this project under the umbrella of Aurelia though

[mhamann]

So, still nobody working on this?

[rdegges]

Yes, this is still on the backburner :(