Sign in

At the end of this guide, you will have working provider buttons on both your login and signup pages, backed by a controller that handles the OAuth round-trip and dispatches the result.

This guide walks you through creating the SocialAuthController, registering the redirect and callback routes, and wiring the provider buttons into your existing login and signup views.

The guide covers:

• Creating the SocialAuthController with redirect and callback methods
• Registering the OAuth routes with formsThrottle on the redirect endpoint
• Adding provider buttons to login.edge and signup.edge
• The four outcomes the callback dispatches: existing user, new user with verified email, new user with unverified email, and email collision

A single button on the login page and a matching button on the signup page both point at the same controller. You do not need separate sign-in and signup routes for each provider. The callback inspects the result of the OAuth round-trip and figures out whether the visitor has an existing account or needs a new one.