Add-On Releases - vBSSO - vBulletin Single Sign-On

vBSSO is a vBulletin plugin that helps you connect to different software platforms like content management systems, blogs, and online stores using a secure Single Sign-On

The system has two components. First, there?s a vBulletin plugin that creates an interface for authenticating, controlling access, and managing user profile data. The second component is plugins for other platforms (like WordPress) that teach it to talk to vBulletin and exchange data. Here?s a list of support platforms.

Supported Platforms (https://www.vbsso.com)

• vBulletin
• WordPress
• WordPress Multisite
• Drupal
• Mediawiki
• Moodle
• Prestashop
• DokuWiki
• Joomla
• Magento

SSO Key Features

• Run across different sub-domains, domains, servers and ports
• Easy setup & configuration
• Automatically log into third party applications when you log into vBulletin
• Automatically log out of third party applications when you log out of vBulletin

Single Sign-On

• Log to third party applications through vBulletin
• Log out of third party applications through vBulletin
• Register to third party applications through vBulletin
• Recover password to third party applications through vBulletin

License

• Free, open source
• GNU general public license, version 2
• Reusable code

Safety

• Encrypted data exchange via private unique shared key
• Friends with firewalls
• Communicates purely through API of the connected platform
• Basic Access Authentication support

Setup & Configuration

• Quick startup
• Advanced configuration options
• Backup & Restore

Avatars

• Sync vBulletin avatars with third-party applications

User Groups

• Restrict access to third-party applications using vBulletin usergroups
• Add visitors of third-party applications to vBulletin usergroups

Miscellaneous

• Custom vBulletin login page
• Custom vBulletin registration page

== Changelog ==

= 1.6.4 =

• Feature #6421: vBSSO | Add PHP 7.1, 72 support. Fixed PHP warnings.
• [Updated on March 26, 2019]

= 1.6.1 =

• Added PHP 5.3, 5.4, 5.5, 5.6, 7.0 support for vBulletin 4.2.
• Fixed an issue when vBulletin throws the Warning: Invalid argument supplied... in case of connecting platforms on different domains/BAA.
• Fixed an issue when user location is shown as unknown on the "Currently Active Users" page.
• Other enhancements and bugs fixes.
• [Updated on July 25, 2017]

= 1.6.0 =

• Added PHP 5.4, 5.5, 5.6, 7.0 support for vBulletin 4.1.x.
• Fixed the issue when download logs function was not working and was displaying an empty white screen (PHP5.6).
• EOL (End-of-life due to the end of life of this version) for PHP 5.2 support.
• EOL (End-of-life due to the end of life of this version) for vBulletin 3.x support.
• Other enhancements and bugs fixes.
• [Updated March 10, 2017]

= 1.5.1 =

• Fixed an issue when vBulletin redirects to WordPress search page after сlearing the browser's cookie and cache.
• [Updated February 19, 2016]

= 1.5 =

• Fixed fatal error on logout operation if logout is initiated from "vBulletin Mobile Suite".
• Enhanced intensive logging to troubleshoot issues with ease.
• Added vBulletin 5 compatibility notifications message on installation.
• [Updated August 31, 2015]
  

= 1.4.16 =

• Added PHP 5.6 support
• Added support of cross-domain single-sign on in Internet Explorer.
• Fixed an issue when vBSSO didn't connect platform with strong www redirect.
• Fixed an issue when vBulletin didn't work as a child platform.
• Fixed an issue when vBSSO widget for Wordpress didn't show the number of notifications due to bug on vBulletin side.
• Other enhancements and bugs fixes.
• [Updated June 04, 2015]

We strongly recommend you to upgrade vBSSO to the latest version (1.4.15)

= 1.4.15 =

• Fixed the potential SQL injection vulnerability that might display md5 version of password (the original password is safe).
• Fixed an issue when sometimes avatars are not fetched and displayed in connected to vBulletin platforms.
• Fixed an issue when some redirects in vBulletin 3.x were processed improperly.
• Fixed an issue when sometimes white screen was displayed after registration.
• Fixed <base> tag for vBulletin 3.x
• Other enhancements and bugs fixes.
• [Updated January 20, 2015]

= 1.4.14 =

• Fixed "Support www alias" option on "Connect Platform" page.
• Fixed <base> tag behavior when "Always use Forum URL as Base Path" option disabled.
• Other enhancements and bugs fixes.
• [Updated November 17, 2014]

= 1.4.13 =

• Implemented possibility to get vBulletin notifications counter through vBSSO.
• Improved avatars rendering method.
• Added usergroups support in vBulletin as connected platform.
• Added a new warning entry to ?Warnings? page identifying vBulletin hooks status.
• Added a new warning entry to ?Warnings? page identifying forum accounts with empty username.
• Added a new warning entry to ?Warnings? page identifying missing PHP extensions.
• Added a new warning entry to ?Warnings? page identifying disabled PHP functions required by vBSSO.
• Added support for authorization both with www and without it.
• Fixed an issue, when the platform couldn?t be disconnnected while uninstalling vBSSO.
• Fixed AdminCP login issue.
• Fixed E_NOTICE errors in debug mode.
• Other enhancements and bugs fixes.
• [Updated November 1, 2014]

= 1.4.12 =

• Made the version compatible with other extensions like "PurevB Theme Manager", "GlowHost - Spam-O-Matic", "PhotoPost vBGallery".
• Added a new warning entry to "Warnings" page identifying forum accounts with duplicated username/email and empty email addresses.
• Added a forum "moderation" page support while user is being registered through vBSSO.
• Logout is not any longer restricted by "Access Settings" configuration.
• Adding "https" domains to forum "whitelist".
• Fixed the "logs in .zip" downloading issue.
• Resolved "Logout" issue for user with no forum access privileges when two forums are connected to each other.
• Adjusted "Access Settings" to handle login access restrictions properly.
• Other enhancements and bugs fixes.
• [Updated June 17, 2013]

= 1.4.11 =

• Prepared the feature to handle broken user accounts between WordPress and vBulletin.
• Enhancements and bugs fixes.
• [Updated May 22, 2013]

= 1.4.10 =

• Added usergroups support in vBSSO vBulletin. Other vBSSO extensions should implement vBSSO vBulletin usergroups API to support usergroups on a connected platform.
• Implemented an ability to login visitors by their email address.
• Improved support of vBulletin SSL mode.
• Improved vBSSO avatars lookup performance.
• Removed unsed 'cssrollup_vbsso.xml'.
• Fixed login issue through vBulletin API. Tapatalk compatible.
• Fixed the issue when "Show vBulletin Profile" option is not being updated in case of connection two forums.
• Fixed the issue when the platform couldn't be connected if "Allowed User Groups" is filled out to restrict login access.
• Other enhancements and bugs fixes.
• [Updated May 20, 2013]

= 1.4.9 =

• Restored the visibility of the activation message showed before user proceeds with login after registration process.
• Improved "Logging & Notifications" section to get much quicker and flexible access to log files.
• Added a special section called "Warnings" to warn administrators about potential issues required to be solved.
• Added tips to "Access Settings" section.
• Improved the verification process in case if we establish forum to forum connection.
• "vBulletin Links" section was renamed to "Link Custom Pages".
• Enhancements and bugfixes.
• [Updated February 01, 2013]

= 1.4.8 =

• Made vBSSO "vBulletin 4.2.0 PL3" compatible.
• Added new supported profile fields "Birth", "Phone".
• Enhancements and bugfixes.
• [Updated October 26, 2012]

= 1.4.7 =

• Extended the authentication and login vBSSO API.
• Added 4 new hooks (vBSSO Login Event, vBSSO Logout Event, vBSSO Authentication Event, vBSSO Register Event).
• Fixed creating user from admincp.
• Fixed Admin Panel menu items order.
• Enhancements and bugfixes.
• [Updated October 26, 2012]

= 1.4.6 =

• Implemented support of SSL.
• Handled endless redirect once it finds non-compatible accounts.
• Fixed the conflict when "Save stylesheets to files" option is enabled in vBulletin 3.x.
• Enhancements and bugfixes.
• [Updated September 23, 2012]

= 1.4.5 =

• Implemented support of avatars for connected vBulletin platform.
• Implemented support of user profile and author links for connected vBulletin platform.
• Adjusted login form for connected vBulletin platform.
• Implemented the feature to update the settings of all the connected platforms as soon as master plugin is upgraded.
• Enhancements and bugfixes.
• [Updated September 03, 2012]

= 1.4.4 =

• Added vBulletin 3.x compatibility.
• Added support of vBulletin connection as slave platform.
• Fixed an issue on adding new user from admincp when it is not added to the connected platforms.
• Fixed "Class 'LoggerReflectionUtils' not found" issue.
• [Updated August 10, 2012]

= 1.4.3 =

• Http status code 100 shouldn't be tracked as error - fixed.
• Adjusted extensive debug logging of the response errors.
• Fixed an issue when sometimes avatars are not fetched and displayed in connected to vBulletin platforms.
• [Updated June 22, 2012]

= 1.4.2 =

• Resolved installation error "Invalid SQL: INSERT INTO `vbsso_users`" thrown in cases when account duplicates exist. We check for the duplicates and throw the warning during the installation phase.
• Fixed Fatal error: Call to undefined function print_cp_header() error when vBulletin is configured to have custom named AdminCP folder.
• Implemented un-installation hook to disconnect all the connected to vBSSO platforms.
• Added a check to warn if vBulletin "User Registration Options -> Require Unique Email Addresses" is disabled and duplicated accounts are allowed.
• [Updated November 17, 2011]

= 1.4.1 =

• Fixed Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'Logger::warning' was given in /vbsso/includes/functions_logging.php.
• [Updated October 10, 2011]

= 1.4 =

• Refined Notifications section, renamed it to Logging & Notifications, added the options to log vBSSO logic, keep logging files and send log messages to email.
• Improved installation process by cleaning up the database before the product is completely installed.
• Improved installation process by adding a check for the required PHP extension before the plugin is completely installed or upgraded.
• Fixed the issue that might be a cause of the empty page in admincp.
• Moved the settings to standard vBulletin Options.
• Moveed Backup & Restore to standard vBulletin Backup & Restore facility.
• Added vBulletin 4.x version as a dependency for the plugin.
• Removed option to set Forum Path.
• [Updated September 28, 2011]

= 1.3 =

• Added sending of the authentication event to the connected platform as soon as user is registered in vBulletin.
• Fixed issue with ':' delimiter located between host and port in url in case of using non-standard port #80
• Added support to redirect to lost password page via API.
• Added config.custom.default.php file as a config sample.
• Fixed "Warning: Call-time pass-by-reference has been deprecated" error.
• Added error message in case if platform couldn't be verified for some reason.
• Removed the extra steps to set up forumpath setting, it's being setup automatically during plugin installation.
• Fixed css to display "SSO provided By" text correctly in different theme layouts.
• [Updated September 18, 2011]

= 1.2 =

• First release
• [Created September 10, 2011]

Project Supported by Diabetes Daily
"We are in dept to those who have donated their code and advice to us over the last six years. Without that support, we would never have built one of the most successful diabetes communities. This is our way of 'paying it forward' so others can do more better and faster." - David Edelman, Co-Founder of Diabetes Daily

Download Now

• vbsso-vbulletin-1.6.4.zip
• vbsso-wordpress-1.4.3.zip
• vbsso-drupal-1.1.2.zip
• vbsso-mediawiki-1.0.2.zip
• vbsso-moodle-1.0.0.zip
• vbsso-prestashop-1.1.zip
• vbsso-dokuwiki-1.1.0.zip
• vbsso-joomla-1.1.0.zip
• vbsso-magento-1.1.0.zip

[tambo]

Originally Posted by Syxguns

...useful stuff...

Thanks for the reply, man. I kinda gave up on Wordpress as it just would not connect properly, however, I have had more success with mediawiki (of a sort), which leads me to...

Originally Posted by xeagle

Dear tambo,

...Could you please clean up "Access Settings"...

Xeagle,

I've managed to get this connected to MediaWiki 1.20.6, however, I'm having some real difficulties understanding what each setting is supposed to do.

You've made something that looks awesome. The downside of that is that you now get a load of demanding people trying to use it!

I need help... but you guys seriously need some step-by-step documentation and definitions! So I figured I'd construct my question in a way that starts making that documentation for you... and you can fill in the blanks.

Things you need to clarify are in red.

Here is my current Vbulletin-MediaWiki set-up:

Step 1: vBulletin Installation

• Upload everything from the unzipped "upload" folder to the `/` root directory of forum (in my case "/vb")
• Log in to forum Admin Control Panel as administrator
• Navigate to 'Plugins & Products' section
• Expand section and click on the 'Manage Products' link
• Scroll down in the right-hand frame until you find 'Add/Import Product' link
• Click on the link and browse for vbsso.xml file
• Click on the import button

Step 2: MediaWiki Installation

• Download MediaWiki vBSSO.
• Unzip and upload everything to `/extensions/vbsso/` directory of your MediaWiki installation.
• Log in to MediaWiki as administrator.
• Open `LocalSettings.php` file in the root of MediaWiki installation and add:
  

  require_once( “$IP/extensions/vbsso/vbsso.php” );

• Make sure that *.conf files are writable. (I see two such files: "platform.conf" and "vbsso.conf" - who should they be writable to? At the point of installation, chmod is set to 644. Is this enough?)

Step 3: MediaWiki Configuration

• Log into Administrator account on MediaWiki installation.
• Navigate to 'Special Pages'.
• At the bottom, under 'Other special pages', click 'vBSSO' and you will be taken to the 'Special:Vbssoconfig' page.
• Fill in the shared platform key to one of your choice (this will need to match what you put in vBulletin in the next step).
• Click Submit.
• Your completed form should now look like this:
  
  

Step 4: vBulletin Configuration

• Log in to forum Admin Control Panel as administrator
• Navigate to the vBSSO section near the top of the left-hand frame
• Expand the section and click 'Connect a Platform'
• Insert the respective details from the wiki's 'Special:Vbssoconfig' page. Your completed form should look like this:
  
  
  
  
• Click 'Connect'.
• After receiving confirmation, you should now have the following connection in green at the bottom of the page:
  
  

At this point, any vBulletin account can successfully log into MediaWiki as a 'User'. However, I would like to restrict this to particular usergroups. In the example below, I go to 'Access Settings' and set the usergroup to 6 (vBulletin Admin usergroup number).



Despite this, it's still permitting access to other usergroups. 'Registered Users' (usergroup 2) are able to log into and edit the wiki.

Further questions that aren't clear to me:

• What do the 'Login Access Setting' do, and why are they arranged in a 2x2 checkbox formation? They don't seem to have an effect.
  
  
• If I were to remove the top-right checkbox (the only one I can toggle in the example above), what is supposed to be the effect?
  
  
• Also, what is the effect of the 'Connection Settings' and 'Master Platform'? On installation, I left it alone, but have since changed it to match the MediaWiki key, as shown below. Again, it has not made much difference.
  
  
  
  
• Assuming the plugin does handle usergroups, how does the plugin handle a change of usergroup? So if I ban someone in vBulletin, is their access revoked in MediaWiki too?

[xeagle]

Originally Posted by tambo

Thanks for the reply, man. I kinda gave up on Wordpress as it just would not connect properly, however, I have had more success with mediawiki (of a sort), which leads me to...

tambo, great start for knowledge base! Unfortunately we admit there is a lack of useful documentation and the summer is a season when vBSSO is committed to change this to the better state.

Regarding to your questions:
Q: Make sure that *.conf files are writable. (I see two such files: "platform.conf" and "vbsso.conf" - who should they be writable to? At the point of installation, chmod is set to 644. Is this enough?)

A: platform.conf and vbsso.conf. In most cases 644 is not enough, because the web application server should have a permission to update those files.

Q: Despite this, it's still permitting access to other usergroups. 'Registered Users' (usergroup 2) are able to log into and edit the wiki.

A: It shouldn't happen, we will check it.

Q: What do the 'Login Access Setting' do, and why are they arranged in a 2x2 checkbox formation? They don't seem to have an effect.

A: It's another type of configuration. For example if there are more than 2 platforms connected to vBulletin it makes sense to log user from WordPress and skip sign-in to MediaWIki for example and it's regulated by checkbox from left(source platform) to right(destination platform).

Q: Also, what is the effect of the 'Connection Settings' and 'Master Platform'? On installation, I left it alone, but have since changed it to match the MediaWiki key, as shown below. Again, it has not made much difference.

A: Connection Settings are used if you want to connect one vBulletin forum to another one and slave forum settings are configured at Connection Settings.

Q: Assuming the plugin does handle usergroups, how does the plugin handle a change of usergroup? So if I ban someone in vBulletin, is their access revoked in MediaWiki too?

A: Latest version of MediaWiki doesn't support usergroups. MediaWiki usergroups support is in progress.

We hope our answers bring more understanding to you.

[Chris Beveridge]

I went to install this on a VB 4.2 install today and in doing the import, it returned these errors:

We have identified the potential buggy hooks / plugins conflicted with vBSSO. If you experience any issues with vBSSO, please resolve the conflicts before contacting the support team.
You need to replace highlighted code with this pattern:
require_once(DIR . '/path/to/plugin/file.php');

Title Hook Location Hook code
GlowHost - Spam-O-Matic: AKISMET SPAM filter newpost_process
require_once('includes/functions_ghsom.php');

GlowHost - Spam-O-Matic: Finish Registration register_addmember_complete
require_once('includes/functions_ghsom.php');
SOM_UpdateLog();
GlowHost - Spam-O-Matic: Registration Pre-Check register_addmember_process
require_once('includes/functions_ghsom.php');
SOM_Process();
GlowHost - Spam-O-Matic: First Post/Thread Control threadfpdata_presave
require_once('includes/functions_ghsom.php');

GlowHost - Spam-O-Matic: Replies Control postdata_presave
require_once('includes/functions_ghsom.php');

Form actions inlinemod_action_switch
require_once('includes/functions_ghsom.php');
SOM_cleanupProcess();

[tambo]

Originally Posted by xeagle

A: platform.conf and vbsso.conf. In most cases 644 is not enough, because the web application server should have a permission to update those files.

666 then?

Originally Posted by xeagle

Despite this, it's still permitting access to other usergroups. 'Registered Users' (usergroup 2) are able to log into and edit the wiki.

A: It shouldn't happen, we will check it.

Hmmm... so, as I understand it, only the array of vBulletin usergroups IDs defined in 'Access Settings' should be provided access to the default "Users" MediaWiki usergroup?

For your info, I'm running vB 4.2.1 and MW 1.20.6.

Do you require access to my test site to verify/compare?

Happy to do so, if needed.

Originally Posted by xeagle

A: It's another type of configuration. For example if there are more than 2 platforms connected to vBulletin it makes sense to log user from WordPress and skip sign-in to MediaWIki for example and it's regulated by checkbox from left(source platform) to right(destination platform).

Understood, thankyou.

Originally Posted by xeagle

A: Connection Settings are used if you want to connect one vBulletin forum to another one and slave forum settings are configured at Connection Settings.

Understood.

Originally Posted by xeagle

A: Latest version of MediaWiki doesn't support usergroups. MediaWiki usergroups support is in progress.

Being able to match specific vB usergroup IDs to specific MediWiki usergroup names (and have a change in the vBulletin usergroup effect a change in the MediWiki usergroup) would be pretty much awesome.

[xeagle]

Originally Posted by Chris Beveridge

I went to install this on a VB 4.2 install today and in doing the import, it returned these errors:

We have identified the potential buggy hooks / plugins conflicted with vBSSO. If you experience any issues with vBSSO, please resolve the conflicts before contacting the support team.
You need to replace highlighted code with this pattern:
require_once(DIR . '/path/to/plugin/file.php');

Title Hook Location Hook code
GlowHost - Spam-O-Matic: AKISMET SPAM filter newpost_process
require_once('includes/functions_ghsom.php');

GlowHost - Spam-O-Matic: Finish Registration register_addmember_complete
require_once('includes/functions_ghsom.php');
SOM_UpdateLog();
GlowHost - Spam-O-Matic: Registration Pre-Check register_addmember_process
require_once('includes/functions_ghsom.php');
SOM_Process();
GlowHost - Spam-O-Matic: First Post/Thread Control threadfpdata_presave
require_once('includes/functions_ghsom.php');

GlowHost - Spam-O-Matic: Replies Control postdata_presave
require_once('includes/functions_ghsom.php');

Form actions inlinemod_action_switch
require_once('includes/functions_ghsom.php');
SOM_cleanupProcess();

Chris, try please go over those hooks ("Plugins & Products" section) and replace the includes in require_once('lib') with the require_once(DIR . '/lib'); where "lib" is included script.

[xeagle]

Originally Posted by tambo

666 then?


Hmmm... so, as I understand it, only the array of vBulletin usergroups IDs defined in 'Access Settings' should be provided access to the default "Users" MediaWiki usergroup?

For your info, I'm running vB 4.2.1 and MW 1.20.6.

Do you require access to my test site to verify/compare?

Happy to do so, if needed.

Understood, thankyou.


Understood.


Being able to match specific vB usergroup IDs to specific MediWiki usergroup names (and have a change in the vBulletin usergroup effect a change in the MediWiki usergroup) would be pretty much awesome.

#1 Just ensure that your *.conf files are writable by application server, so, keep using extension connecting mediawiki to vBulletin.

#2 if 'Access Settings' is specified, yes, access only to those certain usergroups is allowed, otherwise for all.

If you have a more tech questions please don't hesitate to contact vBSSO support team.

[Syxguns]

xeagle-
Has your team been successful in making this modification work with "https" for a member that paid for it? I've been waiting for quite some time. Do I need to take the time to see if I can make the changes to the code myself?

I really like this plug-in but it will not work for me!

Why Is A SSL Certificate Required?

With booming Internet trends and fraud, most will not submit their private details on the web unless they know that the information they provide is securely transmitted and not accessible for anyone to view.

[xeagle]

Originally Posted by Syxguns

xeagle-
Has your team been successful in making this modification work with "https" for a member that paid for it? I've been waiting for quite some time. Do I need to take the time to see if I can make the changes to the code myself?

I really like this plug-in but it will not work for me!

The latests version of vBSSO support https connection between vBulletin and WordPress. So, vBSSO readme.txt was updated for WordPress, please feel free to give it a try.

[tambo]

Originally Posted by xeagle

Q: Despite this, it's still permitting access to other usergroups. 'Registered Users' (usergroup 2) are able to log into and edit the wiki.

A: It shouldn't happen, we will check it.

Were you able to replicate this, or do I need to work on my installation?

Cheers

[xeagle]

Originally Posted by tambo

Were you able to replicate this, or do I need to work on my installation?

Cheers

The issue was replicated and fix would be actually a part of soonest vBSSO vBulletin update with features and improvements.