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

[Cydefense]

Originally Posted by xeagle

The update is under 3rd round of testing and it's going to be published asap to cover some of the issues and bring more useful features like ssl support, usergroups, etc.

Hi,
Can you give ur skype or email, i really want to ask you something

[Blue-Inc]

Cheers. This is working great. Although I do have an issue where my main wordpress account is not the same as my administrator account on my vB forum. It's not a big problem, it's just that admin account on my vB forum and WP site are not linked. (Meaning, I have to keep logging out into my main admin account on WP)

[xeagle]

Originally Posted by Cydefense

Hi,
Can you give ur skype or email, i really want to ask you something

Support is ready to help you with pleasure http://vbsso.com/request-new-feature/. Just contact them

[xeagle]

Originally Posted by Blue-Inc

Cheers. This is working great. Although I do have an issue where my main wordpress account is not the same as my administrator account on my vB forum. It's not a big problem, it's just that admin account on my vB forum and WP site are not linked. (Meaning, I have to keep logging out into my main admin account on WP)

Right, so far vBSSO requirement is to have all the accounts aligned having the same username / email in both system. It's a limitation, however we expect to jump up this year to avoid this limitation.

[tambo]

I've tried so hard to get this mod to work on a test site over the last 6 months, using different versions, different installs, even different servers and hosts... but it just doesn't connect properly.

My intention is to link a wiki, but I've been testing on a wordpress site for the sake of simplicity. The folder structure for these installations is that both sit in their own folder relative to root. So vB is in: "root/forum/..." and Wordpress is in "root/site/...".

On initial installation in both vB and wordpress, I attempt to connect the wordpress platform by taking the values from the Wordpress "vBSSO Settings" page and adding them to the vB "Connect a Platform" ACP page. For example:

Address: http://www.example.com/site/wp-content/plugins/vbsso/vbsso.php
Key: 123456789

On doing this for the first time on a clean vB installation, it appears to validate the connection as the details are added at the bottom of the page and are in lovely green text.

I add the necessary usergroup IDs to the vB "Access Settings" page, but no matter what I do, the account does not log into Wordpress. If I press "login" on the front end of the Wordpress site, the vB "logging you in" screen shows, but does not log me into Wordpress. If I press it again, there is an error message (can't remember what it says, but logfiles suggested that it was because the username already existed???).

On reviewing the previously added connection in the "Connect a Platform" ACP page, the text is now red???

If I delete that platform connection and attempt to re-connect that platform using the same (or different) values, the process no longer succeeds and simply throws an error:

Unable to verify platform [http://www.example.com/site/wp-content/plugins/vbsso/vbsso.php]
Please analyze log files located at `/home/partcser/public_html/example.com/forum/vbsso/logs/` to detect the cause of the issue.

Logs are enabled to show "all" levels of severity, but nothing is recorded regarding this now-failing connection.

I can't understand from the little documentation where I'm going wrong. Like others have indicated, I'm willing to pay for a Pro version of this (or branding free... whatever) as it's a much-needed feature, but I simply cannot get it to work as it's described.

[Syxguns]

tambo,
I had a similar issue at first, and in reading posts learned a couple of things.

1) Make sure that user names are one word and not two. Example: "Mr Robot" is allowed in vB but not on WP. This is primarily because it will break the URL. In other words "Mr Robot" would be translated to "Mr%20Robot". I have not found a work around on this issue. This means that all users on vB that have a space would need to use an underline "_" to make it work which means the name would need to be "Mr_Robot" or "Mr-Robot" would work as well.

2) This mod still does not work for "https", which isn't a problem for you, but I've been waiting for the update. I did pay for the pro version! I'm hoping this will be resolved soon.

Try to completely remove all of the files for the Mod, clean the database for WP, then start from scratch and make sure that there are no spaces in user names. I think periods are fine like "Mr.Robot" because it will should not mess up the URL but I would not suggest it. See if that was the issue.

[xeagle]

Originally Posted by tambo

I've tried so hard to get this mod to work on a test site over the last 6 months, using different versions, different installs, even different servers and hosts... but it just doesn't connect properly.

My intention is to link a wiki, but I've been testing on a wordpress site for the sake of simplicity. The folder structure for these installations is that both sit in their own folder relative to root. So vB is in: "root/forum/..." and Wordpress is in "root/site/...".

On initial installation in both vB and wordpress, I attempt to connect the wordpress platform by taking the values from the Wordpress "vBSSO Settings" page and adding them to the vB "Connect a Platform" ACP page. For example:

Address: http://www.example.com/site/wp-content/plugins/vbsso/vbsso.php
Key: 123456789

On doing this for the first time on a clean vB installation, it appears to validate the connection as the details are added at the bottom of the page and are in lovely green text.

I add the necessary usergroup IDs to the vB "Access Settings" page, but no matter what I do, the account does not log into Wordpress. If I press "login" on the front end of the Wordpress site, the vB "logging you in" screen shows, but does not log me into Wordpress. If I press it again, there is an error message (can't remember what it says, but logfiles suggested that it was because the username already existed???).

On reviewing the previously added connection in the "Connect a Platform" ACP page, the text is now red???

If I delete that platform connection and attempt to re-connect that platform using the same (or different) values, the process no longer succeeds and simply throws an error:

Unable to verify platform [http://www.example.com/site/wp-content/plugins/vbsso/vbsso.php]
Please analyze log files located at `/home/partcser/public_html/example.com/forum/vbsso/logs/` to detect the cause of the issue.

Logs are enabled to show "all" levels of severity, but nothing is recorded regarding this now-failing connection.

I can't understand from the little documentation where I'm going wrong. Like others have indicated, I'm willing to pay for a Pro version of this (or branding free... whatever) as it's a much-needed feature, but I simply cannot get it to work as it's described.

Dear tambo,

At first glance you properly try to connect a platform and your connection issue would be due to the using "https" (https support version is under testing, going to be released asap) or filling up the Access Settings incorrectly. Could you please clean up "Access Settings" and try to connect your platform again. If the problem is persistent for you, please contact a support team (http://vbsso.com/report-an-issue/ it's thankfully free now) and send them temporary access to your forum and wordpress to let them troubleshoot that issue.

Thank you,

[popup]

I am going to use vBSSO with Drupal 6. and have a couple of questions. Sorry if they sound stupid:

- Does vBSSO work with VB 5?
- Is synchronization bi-directional? (I mean people can register to Drupal and get authenticated into VB and vice versa?

- Is banning users goes bi-directional? (Or I need to ban each user in both Drupal and VB?)

- What happens if the same user has different passwords on Drupal and VB? Which set of passwords will be overwritten, if any? (This is the senario which I will have after converting my actual Drupal forum to VB)

Thanks

[Rolll]

Is this version compatible with PHP Version 5.4.4-14?
Because it give me a server error when I try to login, and when I try connect a platform, it's show me a blank page...

[Rolll]

Solved i've installed Php curl.

http://askubuntu.com/questions/9293/...l-curl-in-php5