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

[supercub]

No doubt a DUMB question, sorry... I tried to read this whole thread and could not find the answer anywhere:

Using VB and Drupal - Does the user have to exist in both databases? In other words, when a user signs up for VB, do they also have to have a Drupal login of the same email/user or does this circumvent the druapal user requirement or vice versa?

Sorry to be so dense.

sj

[Syxguns]

Originally Posted by supercub

No doubt a DUMB question, sorry... I tried to read this whole thread and could not find the answer anywhere:

Using VB and Drupal - Does the user have to exist in both databases? In other words, when a user signs up for VB, do they also have to have a Drupal login of the same email/user or does this circumvent the druapal user requirement or vice versa?

Sorry to be so dense.

sj

It's not a dense question. There are a few ways to set it up.

1) You may use the built in forms of vBSSO
2) You may use Drupal
3) You may use vB.
4) You may use a combination of both.

You may set the custom URL's yourself which is what I did.

On my site:
If you select "Register" on Wordpress or vBulletin you will be taken to the vBulletin registration. I have many security features on vB, plus I have a couple of additional questions for new members.

I also set my login and log out page to vB. I then created a detailed explanation with pictures on my home page. You can check it out if you like: http://www.place4musicians.com

I was really happy to find this mod. Now I just got to start building my traffic!

[supercub]

Thanks. So if I understand you correctly, I will not have duplicated user login data between Drupal and VB, or will it be posted automatically? I think what you are saying is that I can use the drupal login to access the VB features, or vice versa without duplicate user data.

The VBSSO website does not seem to have great documentation about this. Is it somewhere that I am missing?

Thanks again!

sj

[Floda83]

I have a question 'bout the htacces. I installed the mod in vbulletin 4.2 and Wordpress 3.5.1. If I want to add a platform via admincp (vbulletin) i get the following error:

Unable to verify platform [http://www.arreat.de/wp-content/plug...sso/vbsso.php] Please analyze log files located at `/srv/www/htdocs/web431/html/arreat/foren/vbsso/logs/` to detect the cause of the issue.

Error message:
code: 500
response: Server error! Server error! The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there was an error in a CGI script. If you think this is a server error, please contact the webmaster. Error 500 www.arreat.de Mon Mar 25 15:02:15 2013 Apache/2.2.17 (Linux/SUSE)
error_string:

I already contacted my hoster and he says, that I have to outcomment "#Options-Indexes" and "#+FollowSymLinks" in my htaccess. Now I searched all through my hole webserver and could'nt find any htaccess with these lines in it. How could I solve the problem? I want this mod so bad

[Syxguns]

Originally Posted by Floda83

I have a question 'bout the htacces. I installed the mod in vbulletin 4.2 and Wordpress 3.5.1. If I want to add a platform via admincp (vbulletin) i get the following error:



I already contacted my hoster and he says, that I have to outcomment "#Options-Indexes" and "#+FollowSymLinks" in my htaccess. Now I searched all through my hole webserver and could'nt find any htaccess with these lines in it. How could I solve the problem? I want this mod so bad

Did you copy the URL and Shared key field from Drupal? The .htaccess is in the vbsso directory of vB. The other .htaccess file is in the location of drupal where you uploaded the files to. I wouldn't think you would want to comment out that information, so you might have to contact vbsso.com to have them take a look at it. just select the "Report an Issue". Create a new user with Admin privileges in drupal and vB so they have access to see the issue.

[Floda83]

Originally Posted by Syxguns

Did you copy the URL and Shared key field from Drupal? The .htaccess is in the vbsso directory of vB. The other .htaccess file is in the location of drupal where you uploaded the files to. I wouldn't think you would want to comment out that information, so you might have to contact vbsso.com to have them take a look at it. just select the "Report an Issue". Create a new user with Admin privileges in drupal and vB so they have access to see the issue.

It's Wordpress, not Drupal, but doesn't matter anyway I think. Yep. i copied the path which the vBSSO Wordpress plugin gave me, but I just get the Error 500. I already checked the both htaccess files, in both there are not such code (which i talked from in the upper post).

I get this Error 500 even if I just copy the url, taken from vBSSO plugin (settings page) installed on the connected platform to my browser. So there seems to be something wrong with the wordpress plugin?

I just wrote a Ticket via "Report an Issue"...

[TiKu]

Could it be that vBSSO for Wordpress has problems with usernames that contain spaces? VB supports such usernames, and vBSSO creates the Wordpress user with spaces in its name. But e.g. the author link of Wordpress (http://www.mydomain.com/author/TiKu/) is without the spaces and therefore Wordpress does not find any article.
Maybe spaces should be replaced by underscores for the user name?

Regards
TiKu

[Floda83]

Hey,

thanks for your help. It really just was, that I have to comment out the "Options -Indexes" in both htacces files (vbulletin & wordpress). So I changed "Options -Indexes" to "#Options -Indexes" - worked out perfectly. Mod is working great now.

[Syxguns]

Originally Posted by Floda83

Hey,

thanks for your help. It really just was, that I have to comment out the "Options -Indexes" in both htacces files (vbulletin & wordpress). So I changed "Options -Indexes" to "#Options -Indexes" - worked out perfectly. Mod is working great now.

That is great to hear. =)

[Syxguns]

I installed SSL Certificate on my site and now this plugin does NOT work properly. I'm hoping for an update especially since I paid for it. Just a warning for anyone with https: on their forum.