Age | Commit message (Collapse) | Author |
|
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.
|
|
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.
|
|
|
|
|
|
|
|
|
|
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.
|
|
F1Access will provide a collection of F1 API methods, rather than
placing all of those methods in F1User as I was originally planning.
|
|
Parts of addAttribute have been implemented in F1User, but I may move it
out into a general F1 API class.
|
|
|
|
|
|
|
|
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.
|