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

[Dark Pulse]

Upgraded to MediaWiki 1.22.2 due to a critical flaw in Mediawiki; now I can't login anymore via VBSSO. It claims it logs in but it does not.

[SirSteve]

I successfully linked my wordpress with vbulletin but when I view the vbSSO settings, the vBulletin Usergroup and Wordpress usergroup are mapped but when I view a specific user, their usergroup is not correct. Any suggestions?

[rwoscott]

Originally Posted by rwoscott

I've recently upgrade my Vbulletin, and mediawiki, and today have install the 2 parts of vbsso for vb and mediawiki.

I'm getting a blank page in the VB admincp on 3 pages.
- Connect a platform
- connection settings
- Access settings.

All the others show up fine.
I've restarted apache, just in case.

Versions:
vbulletin 4.2.0(pl3)
mediawiki 1,20.2
PHP Version 5.3.2-1ubuntu4
curl 7.19.7
mcrypt 2.5.8

Not long after the blank screens appeared, they disappeared again.
But the mod still worked.

I've now upgraded to 4.2.2 (Even with plugins disabled, this mod caused me problems during the upgrade. I had to actually disable the mod as well).

Anyway due to the double posting issue in 4.2.2, I uninstalled VBSSO (and others plugins) in VB, and now I've reinstalled it I need to get to these screens to configure the platform for mediawiki.

I cannot access the above screens, or "Logging and Notification" or "Warnings".
I've read through a fair bit of this thread. Others have had similar issues, but no resolution has been posted.

I have made sure all VBSSO code is accessible, and I have disable all other plugins and it still doesn't work.

Anyone have any ideas how to resolve this?

[rwoscott]

Originally Posted by rwoscott

Not long after the blank screens appeared, they disappeared again.
But the mod still worked.

I've now upgraded to 4.2.2 (Even with plugins disabled, this mod caused me problems during the upgrade. I had to actually disable the mod as well).

Anyway due to the double posting issue in 4.2.2, I uninstalled VBSSO (and others plugins) in VB, and now I've reinstalled it I need to get to these screens to configure the platform for mediawiki.

I cannot access the above screens, or "Logging and Notification" or "Warnings".
I've read through a fair bit of this thread. Others have had similar issues, but no resolution has been posted.

I have made sure all VBSSO code is accessible, and I have disable all other plugins and it still doesn't work.

Anyone have any ideas how to resolve this?

After much trying. I had to set all VBSSO files to CHMOD 755.
Then i restarted apache a few times before it kicked in.
I now have access to all screens.

Works like a bought one.

[pmcpa]

30 days later and the bugs in this mod are still not resolved, or acknowledged by the developer. I would consider this mod "as-Is" "where-is" and "Unsupported"

[TheLastSuperman]

Originally Posted by pmcpa

30 days later and the bugs in this mod are still not resolved, or acknowledged by the developer. I would consider this mod "as-Is" "where-is" and "Unsupported"

Try contacting them again. A Developer may mark a mod as supported but simply forget to check in on it every so often or not at all, this depends solely on the developer respectfully.

Please note that when donating to a developer for a mod, you're doing just that and nothing more or less. This assumption some tend to have that you're entitled to "something" since you donated money is not accurate and is a false assumption - if you donate, then you donate out of the kindness of your heart, that is what a donation is meant to be and you will receive nothing in return unless the developer does so out of the kindness of their heart .

If this SSO "issue" is in fact a major security issue then please let us know and point out where/how you believe it to be so and we'll quarantine the mod and ask the developer to fix. Since there are many other variations of this mod meant to work with systems other than wordpress it will remain up and quite possibly another member may investigate and provide a fix before the developer does, that has happened in the past in other mod threads and will continue to happen .

[pmcpa]

Emailed them a few times, I will PM you the responses....

The issue is that the system allows you to register on either the vBulletin platform or the Wiki Media platform, bypassing normal registration channels and allows attackers to create user accounts. This is the entire point of the software, and it fails.

We have all normal registration paths disabled on our Wiki installs, funneling everything thru vBulletin/vBSSO, and we go thru and clear out 10 accounts a week on the Wiki that were never created within vBulletin. Add to that, as soon as an account is created on vBulletin, vBSSO creates the account on all other platforms, rather then waiting for the account to be approved.

[xeagle]

Originally Posted by pmcpa

Emailed them a few times, I will PM you the responses....

The issue is that the system allows you to register on either the vBulletin platform or the Wiki Media platform, bypassing normal registration channels and allows attackers to create user accounts. This is the entire point of the software, and it fails.

We have all normal registration paths disabled on our Wiki installs, funneling everything thru vBulletin/vBSSO, and we go thru and clear out 10 accounts a wiki on the Wiki that were never created within vBulletin. Add to that, as soon as an account is created on vBulletin, vBSSO creates the account on all other platforms, rather then waiting for the account to be approved.

pmcpa, As far as I have personally uploaded extensions to the vBulletin repository and talked to developers, they didn't confirm that the cause was in vBSSO. Please don't be widely aggressive and rude.

vBSSO is not providing any services and support to you because every time you are extremely rude to them, threaten with different things, blame them. vBSSO didn't sign any contracts with you and you are open to use or do not use vBSSO products.

[xeagle]

Originally Posted by pmcpa

If by threaten you mean report a flaw via email, and wait 30 days to hear nothing, as that's what we did, then maybe you need to re-examine your business model. We even offered to pay for "expedited support" that you said you offered, but you never responded.

Your mod is designed to streamline and make a single sign on. It doesn't work. It doesn't work with current releases of wikimedia as others have pointed out. The mod is flawed.

We have posted the facts here. If you don't like them, fix them. We have the entire email thread. We will post it here (we have forwarded the thread to vBulletin moderators). These are facts.

Why did we post here? To warn others, there are issues, and it's hard to get them fixed. Again, facts. Don't like these facts, find & fix the flaw. Or at least respond in a timely fashion. Don't want to? Remove the "Supported" Icon, and make it known the plugin is "as-is"

We collect all the facts thrown here. MediaWiki changes their versions from time to time and there is a new bug https://bugzilla.wikimedia.org/show_bug.cgi?id=56269 impacted to the extension.

Single sign on between completely different platforms significantly depends on changes in that platforms, hosting configuration, .htaccess configuration, files permissions and a lot of other stuff.

Yes, of course it becomes more complex solution to support this and model is currently revised to publish out much better way to handle this.

[TheLastSuperman]

You guys I meant that as an in-general statement regarding the Donate button here on most modification threads if the developer has entered in a paypal address in his/her settings it had nothing to do with the vbsso site at all... I see now that you meant their but ok so let's just agree to disagree here by reading the below .

I'm assuming that you must manually initiate an upgrade to mediawiki correct? If so then that means you cannot use a newer version with this mod or more specifically you cannot use a version higher than the one used before the bug was introduced until it is fixed (unless that bug has always existed). It's one of those scenarios we see on rare occasions where a mod has not been updated to run on a newer version of vBulletin or php for that matter and if it's someothing a site depends on heavily they tend to not upgrade until the mod is updated to work properly with vB/php version. What that bug states is what you're describing pmcpa and see the comment made on Feb 4th of this year per the link above, seems like a fix is planned for the next release of mediawiki.

xeagle thank you for the links and clarification .