Authentication- an Overview:

[bps-github7]

sort of a mess of an issue. Could use some help with this one from someone with a greater knowledge and or experience developing with promise based, async solutions. I'm doing my best with it but have to admit that I feel lost in the complexity at times.

• async validators for create-account component: validate user's desired display name, which cannot match any existing display names in the users collection. Seems simple enough, but our observable/ subscription based approach worked and now keeps form in a pending/ invalid state. Tried to implement with async await, but its tricky because the validator already returns a promise. Pretty sure there is another way to make an async validator and that is likely the trick to do this, see if other implementation can support async await.

• timing (possibly, promise) based approach for account creation AND sign on: We need to know if a user signed in for the first time, in order to prompt them to provide additional preference data. if they haven't, but chose to be reminded, remind them when they sign in after a set or custom amount of time has passed.

• login methods for google sign in should cross check preference data, and if the user did not provide a custom display name, then update the user record with the most up to date display name from google account

• additional sign in methods: face book, anything else?

• email activation for account in order to comment or post to forum.

• testing for all of this, In particular, make sure that user record is created on first sign in, updated if google user and record exists.

• general: all these methods should have rigorous error handling, that provide informative feedback to user if something goes wrong in the login, logout or account creation process.