search

stormpath / loopback-stormpath

User authentication for Loopback made simple.
10 stars 1 forks source link

A wider version of issue #1 #6

Open adriatic opened 9 years ago

adriatic commented 9 years ago

I created the complete version of LoopBack tutorial intended to be the primary test for LoopBack-Stormpath interface you are working on. This tutorial will be the first encounter of a typical LoopBack user with Stormpath Account Management Services, so I believe that this should be rock solid before sharing with anyone.

At the moment, this sample fails because the ls-getting-started\client\js\services\lb-services code which is generated by ng-lp code generator is unaware of your StrongLoop-Stormpath interface. It seems that you will need to create the ng-lp-sp equivalent generator, which should not be a big deal.

adriatic commented 9 years ago

Until this issue is addressed (or if I made some wrong conclusions and will get corrected) I cannot do any tests. In order to remain helpful, I will take a slightly different path, by creating the servers side code and data models with slc loopback and directly use the Stormpath services on top of that code, without using loopback-stormpath interface. This is taking place in LoopStormDirect repository.

adriatic commented 9 years ago

Here are the references to LoopStormDirect authentication and authorization code that uses LoopBack API:

  1. https://github.com/congral/LoopStormDirect/blob/master/client/js/controllers/auth.js
  2. https://github.com/congral/LoopStormDirect/blob/master/client/js/services/auth.js

Note: Code in 1. is higher level, using the code in 2.

Note: The app in this repository will use hand-made interface to Stormpath API - as I would like to move a bit ahead, without waiting for you to do all is needed here in the loopback-stormpath interface. However, I would appreciate if you can share with me the mappings from the loopback API to Stormpath API, so my hand crafted interface would be basically the same as the real one you are writing.

adriatic commented 9 years ago

I would suggest to have two documents describing the loopback-stormpath interface: one targeting Stormpath users and the other one for LoopBack users. For example the LoopBack user would be surprised to see the following instructions, so let's assume that the current README.md is beig written for Stormpath users.

image