Show HN: Satellizer – Authentication for AngularJS
11–20 of 38 posts
Re: Show HN: Satellizer – Authentication for AngularJS
#12Re: Show HN: Satellizer – Authentication for AngularJS
#13Re: Show HN: Satellizer – Authentication for AngularJS
#14Re: Show HN: Satellizer – Authentication for AngularJS
#15This is very helpful. How about handling validation and errors (e.g. unique account)?
Re: Show HN: Satellizer – Authentication for AngularJS
#16How easy is this to use without AngularJS? Additionally, if not, does anyone know of any alternative JS (or perhaps Python) libraries for what Satellizer does?
Re: Show HN: Satellizer – Authentication for AngularJS
#17Most sites implementing social auth don't do it in the client directly, but as an interface to the oauth and then just trusting that authentication as canon, while simultaneously invoking a non-oAuth login() method at the tail end of the oAuth login. Not sure how this relates directly.
That said, this is a FANtastic, and very necessary module, and hopefully it covers what I think is the most common use pattern.
Re: Show HN: Satellizer – Authentication for AngularJS
#18It looks like there is a good amount of config for handling different providers. Have you check out OAuth.io and its opensource core oauthd?:
https://github.com/oauth-io/oauthd
https://github.com/oauth-io/oauth-js
It's a simple node app and js sdk that lets you handle providers in a standardized way.
I created a ruby omniauth strategy that simplifies multiple provider support on the backend. A similar approach could be applied to any language:
Re: Show HN: Satellizer – Authentication for AngularJS
#19Re: Show HN: Satellizer – Authentication for AngularJS
#20This is a very nice solution and API for the front-end. It took me a couple part-time months to put together a similar (not modularized) solution for a rewrite of Plunker. There is quite a bit of juggling of information to do to pass around the appropriate information between client, server and auth providers that seems to have been nicely abstracted. There were three major challenges for me in my implementation and…
In my app I maintain a users table that has columns (google_account_id, facebook_account_id, twitter_account_id, etc), pointing to individual rows in a separate accounts tables (e.g. google_accounts, facebook_accounts, twitter_accounts etc). When a user adds an existing account_id, I take care of merging the two different users rows, populating appropriately the account_id in one of the rows, then deleting the extraneous users row. I also migrate the existing data referring to the to-be-deleted user row to the one I plan on keeping.