Broken authentication files
Transitional update, 75% complete
in the middle of fixing user service
SSPI seems to be working

Punched some ugly code through to make it work. Not completely pleased with lack of refactoring I was able to do in the user service file.

configurations for sspi are found in the config/settings/auth.js file.
All site actions now route through MainController, which allows global policies to be put in place. The SSPI policy is one of these.
Fix whitespace: TABS > SPACES

Whitespace only commit
Minor commits to sspi policy
Merge the latest sprint10 changes

Merge branch 'sprint10' into sprint10-feature-sspi-merge2
Fix conflicts in auth merge

Merge branch 'sprint10' into sprint10-feature-sspi-merge2

Conflicts:
	api/controllers/AuthController.js
	config/settings/auth.ex.js
Remove errant main/test route
Disable SSPI by default
Comment why we're passing in config

We need it for other services to easily use
Merge terms & conditions config

Merge branch 'sprint10' into sprint10-feature-sspi-merge2
Merge branch 'master' into sprint11-feature-sspi
Remove autocomplete plugin

This plugin never worked and confused comment boxes.
Remove the plugin and all references to it.

Instead migrate to using At.js and Carat.js for interactive
comment boxes.
Move from carat > caret

I'm not good at spelling
Add comments for login controller

Minor, but helpful
Merge login controller fixes
Make @ autocomplete work

This is an initial, WIP commit.

In a comment box, you can now use the `@` symbol to
search for users, projects, or wikipedia entries.

Support for saving and parsing the text is not yet provided.

But the UI component works.

This required a number of changes:
- sources now provide a `link` field so you know how to link to it
- removed profile source because usernames are emails and should
  not be exposed
- overrode the At.js library to use underscore templates instead
- added CSS for At.js (basic, not styled)

Things that need to be done:
- Styling for dropdown results (eg, user photo, wikipedia, etc)
- Saving div/textarea data to the database
Check userid is finite

Otherwise node throws a fatal error, which crashes
the server.  That's not good.  So check that it is a
finite number before querying the database.
Save comment to database

Store the comment text in the data object (the HTML) so
that it is sent on to the database and renders correctly
when it comes back.  Currently stored as HTML; in the future
it should be stored as some sort of markup that can make
sure the names/usernames display their current values.
Same thing for project names.

But for now, this is probably good enough.  Saving and
retreiving and rendering all seems to work.