Navigate/Search

Archive for the 'Firestorm' Category

Firebase Authorization – User Accounts Links

Friday, November 6th, 2015

To be clear when you want to set up Firebase Authorization you must do two things:

  1. Set Up Accounts
  2. Set Up Rules

This post is about setting up accounts.

You have a lot of choices when it comes to setting up accounts.  You can have your own accounts.  That means that users enter their emails address and passwords.  Then Firebase manages it for you.

Another option is to use an existing system.  Examples of existing systems are gmail, twitter, and facebook.

Basically, when someone logs into their existing account they are logged into your application too.  Then when you save user specific data you just save their account name along with it and you can use that account name to query with.

I chose to use gmail.  Technically this means that a user can’t log into my site if they don’t have a gmail account… I am fine with that.

There are two important links:

As far as I can tell (at this time) the google one is a bit out of date so getting the app working is going to be tricky.

 

Firebase Authorization – User Accounts

Thursday, November 5th, 2015

I am very new to Firebase but one thing I am very excited about is their authorization schemes.  If it’s the way I think it is it’s pretty awesome.

From a user perspective it’s very convenient.  Basically, if you log into gmail (or one of the other supported apps like twitter, facebook, github) you’re logged into my app.

That’s very cool, because you don’t have to remember another user name an password.

From a developer perspective it’s nice because I don’t need to store user names and passwords.  I don’t need to support people forgetting their user credentials.  I don’t need to worry about salts or hashes… gmail handles all of that.

That’s the good stuff.

The bad stuff is that users get confused.  They think that my app might have their gmail password.  They think that I might have access to their gmail…  It’s confusing from a user’s perspective.

Another bad thing is that if Google changes things (well when) it will break my app.

Another bad thing is that setting it up is a moving target and it’s hard to document exactly how to do it because after a bit of time the documentation will be wrong.

For me it good way out weighs the bad because if I don’t have to build a login system that saves me time.  I can roll out a new app in way less time.  What might have taken me a week if you build it yourself or two now takes a few minutes.

Then you can uniquely identify users by their gmail user name.

Coding Firebase Authorization

Wednesday, November 4th, 2015

I have crazy ideas about things I want to build but before I get them built I have another crazy idea.

The thing that is holding me up is back end development.  Especially setting up user authorization.

I think this problem might be over.  I think the idea of setting up a fully functional back end with user authorization in 15 is very possible with Firebase..

I have to overcome two challenges first.

First, I need to figure out how to set up Google Apps for Authorization purposes.

Second, I need to figure out how set up authorization in Firebase itself.

There are a couple of issues for me.  I find this kind of programming to be especially difficult.

In this case, the instructions that describe how to set up a Google App are slightly out of date (I think) and that’s something that bugs me… but that’s how everything is these days.

The way rules are set up seems to be very intuitive because all you have to do is set up a security JSON that is mapped exactly like the actual data structure.