OAuth2 flow is complete but lacks security checks regarding tokens and sessions.

GoogleUtility loads a Discovery Document from google containing:

Endpoints for authenticating users, and for requesting resources including tokens, user information, and public keys.
Removed debug from routes as this html is removed also
Upgraded scala from 2.10.4 to 2.11.1

Added sbt dependencies for deadbolt that functions as a security asset for the application
Added delete link on user page for debugging purpeses
Added delete method
added variables User and String to user.scala.html
added variables User and String and shows a message if user != null
Added String id for the constructor
Updated the error page so it displays an proper error message
Deleted unecceserry html pages
GoogleUtitlity that represents a Discovery Document

The OpenID Connect protocol requires the use of multiple endpoints for authenticating users, and for requesting resources including tokens, user information, and public keys.

To simplify implementations and increase flexibility, OpenID Connect allows the use of a "Discovery document," a JSON document found at a well-known location containing key-value pairs which provide details about the OpenID Connect provider's configuration, including the URIs of the authorization, token, userinfo, and public-keys endpoints.
Google OAuth2 using Open ID Connect

The flow is complete only remaining fixes are the validation with use of signature and encryption, and session handling