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

[xeagle]

Originally Posted by migratoria

I have disabled vbsso because i have installed vb5.4
Now i have the problem of access to wordpress accounts

If re-enabled the plugin to remove the configurations I get this error:

Fatal error: Call to undefined method Composer\Autoload\ClassLoader::setApcuPrefix() in /web/wp-content/plugins/vbsso/vendor/composer/autoload_real.php on line 39


How can I re-enable the plugin or completely uninstall the fields in the db?

Thank you for reaching out.

We regret to hear that you have stopped using vBSSO product.

To uninstall the plugin completely, please (skip 2 first steps in case you are getting error during pugin enabling):
1. Disconnect your platforms;
2. Uninstall vBSSO via Admin Panel;
3. Delete vBSSO files via FTP manager (if needed).

If you need any assistance please feel free to contact our support team.
We will do our best to help you.

[bfdzio]

Originally Posted by xeagle

vBSSO will create TEST USER on WordPress automatically.

Bingo, that is exactly what I was looking for. That is how aMember works and I'm thinking that the issue we were having is actually just because it was my "test" account (literally named test). For some reason, that account causes problems on these things. Same with the aMember user creation.

Originally Posted by xeagle

Regarding your login issue - it seems you have not added vBSSO widget on your WordPress site. Could you please check this out? This widget is required (WordPress > Appearance > Widgets > add vBSSO Login widget to you widget area):

- it will redirect your users to vBulletin`s registration page and let them pass the registration on vBulletin
- vBSSO will add newly registered user to WordPress automatically

In case additional help please contact our support team to submit a support ticket and we will do our best to help you.

Thank you,

I have the widget set up and was using that.

All registration happens on vBulletin for me, and I actually don't need people to login from Wordpress other than just convenience. Any way, I think the issue is just with that particular account because my main account I can login from.

[xeagle]

Originally Posted by bfdzio

Bingo, that is exactly what I was looking for. That is how aMember works and I'm thinking that the issue we were having is actually just because it was my "test" account (literally named test). For some reason, that account causes problems on these things. Same with the aMember user creation.



I have the widget set up and was using that.

All registration happens on vBulletin for me, and I actually don't need people to login from Wordpress other than just convenience. Any way, I think the issue is just with that particular account because my main account I can login from.

Thank you for feedback,

Can you check out that particular account?
- it should exist on your WordPress and vBulletin sides;
- it should has one similar email address;
- it should has one similar password;
(- please check out sso access settings - the group your test user belongs to is allowed to be logged in WordPress? vBSSO > Access Settings > WordPress should be enabled)

Please check out these conditions (fix manually if needed) and your test account will be able to log in both platforms.

After enabling vBSSO and platform connection - your new registered accounts will bу added to WordPress automatically (with one similar email and password) and will be able to use sso.

[bfdzio]

Originally Posted by xeagle

Thank you for feedback,

Can you check out that particular account?
- it should exist on your WordPress and vBulletin sides;
- it should has one similar email address;
- it should has one similar password;
(- please check out sso access settings - the group your test user belongs to is allowed to be logged in WordPress? vBSSO > Access Settings > WordPress should be enabled)

Please check out these conditions (fix manually if needed) and your test account will be able to log in both platforms.

After enabling vBSSO and platform connection - your new registered accounts will bу added to WordPress automatically (with one similar email and password) and will be able to use sso.

Ok so the actual issue is just that I need to get the accounts that are already registered into Wordpress. Is there a simple way to pull that off?

[xeagle]

Originally Posted by bfdzio

Ok so the actual issue is just that I need to get the accounts that are already registered into Wordpress. Is there a simple way to pull that off?

Unfortunately, vBSSO can not check out the users that were registered before connecting the platforms - you should check those users manually or add some script.

If you need assistance with such script implementation we can propose our help (this is paid feature). Please contact our support team if you are interested.

Thank you for using vBSSO product.

[precharge]

Tried installing, wordpress works fine but on vbulletin 4.2.5 get this error

PHP Fatal error: Cannot use $this as parameter in /var/www/html/vbsso/vbsso.php on line 415

[precharge]

Originally Posted by precharge

Tried installing, wordpress works fine but on vbulletin 4.2.5 get this error

PHP Fatal error: Cannot use $this as parameter in /var/www/html/vbsso/vbsso.php on line 415

I was able to get it working.

That said, is if possible to have Wordpress act as a master? Or at least use its user data?

[xeagle]

Originally Posted by precharge

Tried installing, wordpress works fine but on vbulletin 4.2.5 get this error

PHP Fatal error: Cannot use $this as parameter in /var/www/html/vbsso/vbsso.php on line 415

Hi, there,
thank you for reaching out.

We regret to hear that you have an issue with vBSSO product.

Could you please contact vBSSO support team http://vbsso.com/report-an-issue/ describing the steps you use to reproduce your case on your website (please add as more information as you can - both site urls, steps how to reproduce the issue, screenshots etc).

We will do our best to help you.
Thank you for using VBSSO.

[xeagle]

Originally Posted by precharge

I was able to get it working.

That said, is if possible to have Wordpress act as a master? Or at least use its user data?

Thank you for reaching out!

If you are intersted in SSO product where Wordpress act as a master please review SSO vBulletin plugin - where WordPress holds the master users database and all the user-related operations are managed there.

Please find details here --> https://wordpress.org/plugins/sso-vbulletin/ or contact our support team to get more details.

Please do not hesitate to contact us in case of any issues.
Thank you,

[aminp30]

hi

I updated to latest version but I have a problem.
I have to use smtp method to mailing. in registration page after send register button I got this message:

PHP Warning: stream_socket_enable_crypto(): SSL operation failed with code 1. OpenSSL Error messages: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed in ..../includes/class_mail.php on line 776

PHP Warning: Cannot modify header information - headers already sent by (output started at ..../includes/class_core.php:6075) in ..../vbsso/vendor/com.extremeidea.vbsso/vbsso-connect-shared/sharedapi.php on line 281

PHP Warning: Cannot modify header information - headers already sent by (output started at ..../includes/class_core.php:6075) in ..../vbsso/vendor/com.extremeidea.vbsso/vbsso-connect-shared/sharedapi.php on line 281

PHP Warning: Cannot modify header information - headers already sent by (output started at ..../includes/class_core.php:6075) in ..../vbsso/vendor/com.extremeidea.vbsso/vbsso-connect-shared/sharedapi.php on line 281

PHP Warning: Cannot modify header information - headers already sent by (output started at ..../includes/class_core.php:6075) in ..../vbsso/vendor/com.extremeidea.vbsso/vbsso-connect-shared/sharedapi.php on line 281


PHP Warning: mail(): You are not allowed to send emails via PHPMail. For more information contact your server administrator in ..../vbsso/includes/functions_logging_log4php.php on line 92

how can I fix this problem?