foursquare-grow.git - The Foursquare (now Motion Church) Grow website

Age	Commit message (Collapse)	Author
2016-03-22	Integrating the ProgressReporter	Jesse Morgan
	Using the new ProgressReporter interface in AssessmentResultsPage and ChapterCompletePage.
2016-03-21	Introducing the ProgressReporter interface.	Jesse Morgan
	A ProgressReporter will be used to record progress in the ChMS. The F1 version in complete, but needs to be plugged into AssessmentResultPage and ChapterCompletePage.
2016-03-20	Adding support for Church Community Builder login.	Jesse Morgan
	Beginning with this change all of the Church Management System integration logic is moving into implementations of the new IntegrationDriver interface. The desired IntegrationDriver can be selected by setting the integrationDriver config to the appropriate class name. This commit is only moving login support. Progress reporting will move in a later commit.
2014-10-04	Adding metrics.	Jesse Morgan

2014-09-27	Adding F1 Attribute Backfill Tool.	Jesse Morgan

2014-09-27	Adding support to fetch attributes for a user.	Jesse Morgan

2014-09-21	Removing comment.	Jesse Morgan

2014-09-21	Adding Support for Assigning Attributes in F1.	Jesse Morgan
	Adding a new interface, F1API for F1 APIs which require a valid access token. This is now used by AssessmentResultsPage to assign an attribute each time someone completes the assessment. Also adding an AttributeTool to list all attributes and assign attributes to users.
2014-09-09	Moving F1OAuthHelper to F1Access.	Jesse Morgan
	F1Access will provide a collection of F1 API methods, rather than placing all of those methods in F1User as I was originally planning.
2014-08-28	Rough outline of the F1 attribute logic.	Jesse Morgan
	Parts of addAttribute have been implemented in F1User, but I may move it out into a general F1 API class.
2014-02-01	Fixing resource leak.	Jesse Morgan

2014-02-01	Changing user identifier from email to F1 user id.	Jesse Morgan

2013-09-03	New account page improvements and renumbered questions.	Jesse Morgan

2013-08-27	Introducing F1 Authentication and Adding Site Content.	Jesse Morgan
	This change introduced the f1oauth and jesterpm oauth packages for interacting with Fellowship One's developer API. I have also reworked the login authentication to verify credentials through F1 and added session management to track logged in users. The Authenticator chain works as follows: on every page load we check for a session cookie, if the cookie exists, the Request is marked as authenticated and the OAuthUser object is restored in ClientInfo. If this request is going to an account page, we require authentication. The LoginFormAuthenticator checks if the user is already authenticated (via cookie) and if not redirects the user to the login page. When the login form is submitted, LoginFormAuthenticator catches the POST request and authenticates the user through F1. I'm also adding a new account page, but it is currently a work in progress. This commit also adds Allen's content to the site.