Authentication

[sarahhodne]

So, OAuth authentication isn't really implemented yet in the API, so this is the way I think it's going to work.

1. You hit "Sign in" in the app
2. The app authenticates with GitHub somehow (see below).
3. The app authenticates with the Travis API through the /auth/github endpoint.
4. Profit! (Or something) 💵

The GitHub login can be done in many ways, and I haven't quite decided which way I like the best.

• We could open the user's browser to the GitHub login page (or it'll just ask you to approve the Travis Mac App otherwise).
• We could make a smaller web view of some sorts.
• We could make our custom login form and then log in to GitHub with HTTP Basic authentication and get a token from that.

So, what option do you think is the best? And what features do you want to see once we have authentication. This is what I've thought of so far:

• Automatically add your repos to the watch list (<yourusername>/*).
• Trigger rebuilds for repos you can rebuild.

[rkh]

It would also be possible to start a local web app running travis-sso, as localhost is whitelisted. Though I'm not sure if we'll keep it that way.

Alternative would also be to implement OAuth app registration for travis-api. ;)

[sarahhodne]

I'll make sure to keep the authentication logic separate so we can swap it later should that be something we want.