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 409industries

So excited that vBSSO has been updated to work with Wordpress 3.9! I wasn't sure when or if this was going to happen but am very pleased to hear about the new release.

I have since installed both components (vBulletin 4.2.2 and Wordpress 3.9.1) and the SSO part is functioning. However, when vB users are logged in and come over to the Wordpress site, they are not assigned the role of "Subscriber" as indicated on the vBSSO settings.

ALL vBulletin usergroups are configured to be "Subscribers", but when I view my users in WordPress their assigned roles all indicate "NONE"

How can I correct this so that once users are signed in they have the correct role on the wordpress side? This is important as there are specific viewing permissions that are setup on the WP page that aren't working because these users are not considered "subscribers"

Thanks for putting together the new version, I am planning on paying the branding license fee if we can get this sorted out!

See attached screenshots of my vBSSO settings, and Wordpress User list.

Our support team still waiting for a way to log into your server so that we can access the application files for a support request.
Could you please share temporary access to your ftp to check an issue?

[409industries]

Originally Posted by xeagle

Our support team still waiting for a way to log into your server so that we can access the application files for a support request.
Could you please share temporary access to your ftp to check an issue?

My apologies, i would have sent this information over earlier had i been contacted by email. I did not see any response from the "Report an issue" form that i filled out on the vbsso homepage.

I will Private Message over a FTP login you can use access the application files to investigate the problem further.

[Jo_RHU]

Hi, I just installed this to test out on vb 3.8.5.

When I go to these pages:

Connect a Platform
Connection Settings
Access Settings
Logging & Notifications
Warnings

I receive these errors:
Is this because the vb version is so old?

Deprecated: Assigning the return value of new by reference is deprecated in /path/to/my/forum/includes/init.php on line 55

Deprecated: Assigning the return value of new by reference is deprecated in /path/to/my/forum/includes/init.php on line 107

Deprecated: Assigning the return value of new by reference is deprecated in /path/to/my/forum/includes/init.php on line 111

Deprecated: Assigning the return value of new by reference is deprecated in /path/to/my/forum/includes/init.php on line 119

Deprecated: Assigning the return value of new by reference is deprecated in /path/to/my/forum/includes/init.php on line 130

Deprecated: Assigning the return value of new by reference is deprecated in /path/to/my/forum/includes/init.php on line 134

Deprecated: Assigning the return value of new by reference is deprecated in /path/to/my/forum/includes/init.php on line 142

Deprecated: Assigning the return value of new by reference is deprecated in /path/to/my/forum/includes/init.php on line 211

Deprecated: Assigning the return value of new by reference is deprecated in /path/to/my/forum/includes/init.php on line 389

Deprecated: Assigning the return value of new by reference is deprecated in /path/to/my/forum/includes/class_core.php on line 2552

[m7sen]

Originally Posted by xeagle

You can use `vBSSO Access Settings` to limit vBulletin groups that can login via Single Sign-On. If all fields on this page are empty, everyone can login through vBSSO. If you set `Allowed WordPress User Groups` as 6, it means that only administrators will be authorizated in connected Wordpress through vBSSO.

see the pic!
do I have to activate this option ?

and i put all groups in Allowed WordPress User Groups

but still tell the users

PHP Code:

We are sorry, we are not able to process the operation further. Your account should satisfy the single sign-on requirements. Please contact your administrator to solve this issue. 


If i empty all fields on vBSSO Access Settings page
all users groups cam be login wordpress from vbsso login ??
coz i give all users the wp-admin link to login wordpress by vbulletin username

and i do the Settings from wordpress vbsso Settings groups !!:erm:

[xeagle]

m7sen, just leave all vBSSO Access Settings by their defaults (all text fields are empty and all checkboxes are checked) and everything will work as you wish.

If i empty all fields on vBSSO Access Settings page
all users groups cam be login wordpress from vbsso login ??

Yes, but all checkboxes must checked.

[xeagle]

Originally Posted by Jo_RHU

Hi, I just installed this to test out on vb 3.8.5.

I receive these errors:

Is this because the vb version is so old?

you just have to exclude E_DEPRECATED errors to show.

[A.Chakery]

Hello,

First let me thank you for this great plugin...

I have an issue with this plugin (WP integration) , When someone register in vBulletin , after the redirect page it gives me this error :

Fatal error: Call to undefined function fetch_seo_url() in /home/user/public_html/forum/vbsso/includes/functions_api.php on line 361

======= EDIT ========

I sorted it out

Thank you again

[A.Chakery]

I have an issue with saving a new avatar in vbulletin,

When I upload a new avatar and save it, it gives me this error in the redirection page :

PHP User Warning: tempnam() [function.tempnam]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/user:/usr/lib/php:/usr/php4/lib/php:/usr/local/lib/php:/usr/local/php4/lib/php:/tmp) in ..../includes/class_dm_userpic.php on line 204

PHP User Warning: fopen() [function.fopen]: Filename cannot be empty in ..../includes/class_image.php on line 333

do you have any idea how to solve it ?

==== edit ====

I also noticed an another issue ... all vbsso url instances have an additional "/" (slash)... for example here is how the logout url looks like (I marked it with red) :

http://domain.com/forum//vbsso/vbsso.php?a=act&do=logout&d=http%3A%2F%2Fdomain.com%2F&lid=54129ccf8aae47.84842196

and my other question is that is it possible to rewrite vbsso urls in wordpress and vbulletin ?

Thank you.

[xeagle]

Originally Posted by A.Chakery

I have an issue with saving a new avatar in vbulletin,

When I upload a new avatar and save it, it gives me this error in the redirection page :

PHP User Warning: tempnam() [function.tempnam]: open_basedir restriction in effect. File() is not within the allowed path(s): (/home/user:/usr/lib/php:/usr/php4/lib/php:/usr/local/lib/php:/usr/local/php4/lib/php:/tmp) in ..../includes/class_dm_userpic.php on line 204

PHP User Warning: fopen() [function.fopen]: Filename cannot be empty in ..../includes/class_image.php on line 333

do you have any idea how to solve it ?

It is not vBSSO issue. You just have to configure vBulleitn. To resolve it set
Admin CP -> vBulletin Options -> Server Settings and Optimization Options -> Safe Mode Upload Enabled -> Yes
Then go to Admin CP -> vBulletin Options -> Server Settings and Optimization Options -> Safe Mode Temporary Directory and set the right path to your tmp folder (ask your hosting administrators if you don't know)

Originally Posted by A.Chakery

I also noticed an another issue ... all vbsso url instances have an additional "/" (slash)... for example here is how the logout url looks like (I marked it with red) :

http://domain.com/forum//vbsso/vbsso.php?a=act&do=logout&d=http%3A%2F%2Fdomain.com%2F&lid=54129ccf8aae47.84842196

Go to Admin CP -> vBulletin Options -> Site Name / URL / Contact Details, find `Forum URL` and remove `/` at the end of the URL

Originally Posted by A.Chakery

and my other question is that is it possible to rewrite vbsso urls in wordpress and vbulletin ?

Thank you.

Yes. You can do this by adding mod_rewrite rules to .htaccess file.

[A.Chakery]

Thank you for the reply,

Enabling Safe mode solved my first problem,

Go to Admin CP -> vBulletin Options -> Site Name / URL / Contact Details, find `Forum URL` and remove `/` at the end of the URL

I have already set my forum URL without trailing slash ... what would you recommend ?


And regarding the URL rewrite : Thank you for the note but the problem is that vbsso urls are dynamic (I mean log out and such) so there should be a some kind of plugin which force re-writing the url like what vbseo or dbseo are doing.

Thank you again