ConcourseConnect

Open Source Initiative (OSI) PostgreSQL Java

Multiple options for handling user registrations

Posted by Matt Rajkowski on November 23, 2011 9:00 AM EST
Default user photo

ConcourseConnect has several features when it comes to user registrations.

On an open system, users are free to register and become users. There are two default safeguards: the first is that the user must correctly fill out a captcha, and the second is that the user must validate the account by following a confirmation link sent by email.

An additional option is for the administrators to approve all sign-ups. With this option enabled, the user signs-up as normal, and then the administrators receive the confirmation link in which they can approve or deny. This feature has proven useful for semi-open communities in which there public content and you want specific users to register.

Linking your site to Facebook's Login is another option. When you configure both the ConcourseConnect system and the Facebook API with your site's information, users are presented with an option to "Login with Facebook." This option allows users instant access to your site, while Facebook provides all of the validation and authorization of your users. I like this option because Facebook has already verified your user in some way.

ConcourseConnect also has its own token-based sign-up which allows for ConcourseConnect to be plugged into existing websites. In this case your existing site already has user logins, and with some basic programming, site users see a button, called anything you want, which allows one-click access to ConcourseConnect. The sites communicate user information behind-the-scenes and users flow freely from one site to the other.

Finally, a completely closed system means that only administrators and certain users with permission can invite users to the system. In this case the registration feature is turned off and users must fill out a request to become a user.

Now that you have users in your system, my followup blog post explains how to handle the ones that got through your filters.

There are no comments

Sign in to add your comment.

Recent Posts

What version are you on? ConcourseConnect Has 70 Releases So Far In 2017
Are you on the latest ConcourseConnect? As of August 2017 we've had 70 releases which include...
read more
Resources for integrating sites and mobile apps with ConcourseConnect
Here's the latest integrations and developer resources for ConcourseConnect: Android Apps...
read more
New Feature Roundup for June 2016
This is the first feature roundup so this will mostly be a list of improvements and changes to...
read more
ConcourseConnect Mobile API Overview
The ConcourseConnect User API includes RESTful methods intended for 3rd party applications to...
read more
Community statistics and community management improvements
Understanding your community is an important function of community management. The ConcourseConnect...
read more
Badges: More than just personalization – functionality too
In ConcourseConnect, badges are images, logos, or other visual elements that connote affiliations,...
read more
Web app monitoring in ConcourseConnect
Updated July 28, 2014 to include Domain Name expiration monitoring ConcourseConnect includes...
read more
How to disable users or remove them completely
For any number of reasons, a user may need to be disabled or removed from the system. There are...
read more
Multiple options for handling user registrations
ConcourseConnect has several features when it comes to user registrations. On an open system,...
read more
Documentation for ConcourseConnect
As part of Concursive's initiative to provide a simple, cost-effective solution for social business...
read more

Go to blog