Version: 1.6.4, by xeagle
Developer Last Online: Apr 2019
Category: Add-On Releases -
Version: 4.x.x
Rating:
Released: 09-17-2011
Last Update: 06-27-2014
Installs: 242
DB Changes Uses Plugins Auto-Templates
Re-useable Code Additional Files
No support by the author.
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.
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".
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 byDiabetes 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
took me too much to answer, im really sorry, i managed to fix the error by deleting one user haha, and now VBSSO is up and running in two of my wordpress sites i <3 this hack, thank you very much for the help
Sounds great that you have got this working to manage single sign on for all your sites
From the looks of the drop downs on the request feature page, it seems that Mediawiki is on the agenda for a plugin in the future. One thing I am interested in though is if it'd be able to connect an already existing user database (from Mediawiki, or any other system) to the vBulletin database (and allow for a single sign-on), so that people who already have accounts on both would simply be linking their accounts, rather than creating a whole new account. One thing that was a dealbreaker for us with similar modifications in the past is that we use an addon to allow our forum members to change their username, which doesn't work when the addon only matches exact usernames. We'd be looking for something which matches on the forum side based on the user ID number.
From the looks of the drop downs on the request feature page, it seems that Mediawiki is on the agenda for a plugin in the future. One thing I am interested in though is if it'd be able to connect an already existing user database (from Mediawiki, or any other system) to the vBulletin database (and allow for a single sign-on), so that people who already have accounts on both would simply be linking their accounts, rather than creating a whole new account. One thing that was a dealbreaker for us with similar modifications in the past is that we use an addon to allow our forum members to change their username, which doesn't work when the addon only matches exact usernames. We'd be looking for something which matches on the forum side based on the user ID number.
Agreed. So far the plugin is quite good to start a network up quickly from scratch based on vBulletin and WordPress platforms.
From other hand we are in internal brainstorm period of thinking to connect already existing accounts and letting users to change their username and email address in platforms.
If somebody opens to share the vision how they would like to see this, that's greatly appreciated!
What happens if a user changes their password on wordpress or on vbulletin?
vBSSO actually hides user profile inputs to change password in WordPress. In meantime user is free to change its own password in vBulletin and use it further.
vBSSO doesn't touch passwords in WordPress and single sign-on is relied on passwords stored in vBulletin users database only. Thereby, the passwords in WordPress stay untouched / unchanged as they were prior vBSSO plugin is activated.
Hello, Please I have installed your mod and it is fine but when i login it gives me redirect and remains like that without redirecting.
I also now not able to open my wp-admin it is giving me redirecting of vbulletin
You did create accounts and did not specified email address for each registered one. Make sure you have email specified, additionally have no duplicated accounts (accounts with multiple similar email addresses) and your administrative WP account matches to your vBulletin account (username and email).
when click on "Platforms" or/and "Access Settings" in vBSSO menu:
Code:
Fatal error: Call to undefined function print_cp_header() in /<path>/vbsso/includes/functions_template.php on line 19
No logs produced in vbsso/logs (loging level "ALL")
EDIT:
Code:
Tue Oct 18 19:45:54 2011,249 [2323] WARN localFileLogger - PHP Unknown Type: [8192] Function split() is deprecated on line 4 in file /<path>/forum.php(651) : eval()'d code. PHP 5.3.6-nmm1 (Linux)
Tue Oct 18 19:49:26 2011,562 [2327] DEBUG localFileLogger - Method execution [vbsso_db_update_vbsso_user_email]: 0/
Tue Oct 18 19:50:58 2011,551 [5625] WARN localFileLogger - PHP Unknown Type: [8192] Function split() is deprecated on line 4 in file /<path>/forum.php(651) : eval()'d code. PHP 5.3.6-nmm1 (Linux)
not quiet sure about this error since line 4 in forum.php is the commented vB versin and licence number?!
other notes: Admin and Mod CP are in custom named folders. vBSSO's "admincp" folder has been renamed accordingly.
Other mods installed:
Change Author And Date 2.2
DownloadsII 6.0.8
KeyCAPTCHA 3.6.0
Mod-Mall.com Remember Me 1.0.0
More Share Options for VB4 by BOP5 Light 2.6
Remove quoted images and videos 1.1
RSS items as posts 0.6
Separate Sticky and Normal Threads 1.1
Skimlinks-Add-on 2.0.7
Steam Connect [BETA] 1.2.1
Tabs en vBulletin 4.x 2.0.3
Thread Starter in Postbit 1.0.3
Usergroup Color Bar 2.1.1
vBadvanced CMPS 4.1.2
vBGamez Lite 4.0.4
vBSSO Single Sign On 1.4.1
Got the exact same error as this member posted on previous page, did you find a solution to this?.
vBSSO actually hides user profile inputs to change password in WordPress. In meantime user is free to change its own password in vBulletin and use it further.
vBSSO doesn't touch passwords in WordPress and single sign-on is relied on passwords stored in vBulletin users database only. Thereby, the passwords in WordPress stay untouched / unchanged as they were prior vBSSO plugin is activated.
So does that mean existing users are automatically enabled in wordpress?
I wanted to make sure that this is 100% compatible with wordpress plugins and themes.
Got the exact same error as this member posted on previous page, did you find a solution to this?.
Thanks.
vBSSO doesn't support custom named "admincp" folders originally, but, please be patient and new update of vBSSO is coming within a few days where these issues are taken care of.
vBSSO - vBulletin Single Sign-On Details »»
About Developer
DB Changes 
No support by the author.
11-01-2011, 06:07 AM
i <3 this hack, thank you very much for the help
