The Hybridauth module has been installed along with Hybriduath 2 library dependencies. When you attempt to activate login to the Drupal site via the Twitter feature/button, the module requires you acquire the client ID and client secret and pass back the CALLBACK URL. The Hybridauth module requires you provide a specific URL and it is spelled out for the website designer by the configuration screen

http://mydomain.com/hybridauth/endpoint?hauth_done=Twitter

This format seems to be the norm as it is also the same callback URL format required to activate Facebook authentication/login/registration and Google but it is NOT stipulated for all of the other social media providers furnished in the module.

The problem when going to the Twitter API Developer Services console is that Twitter does NOT ACCEPT A QUERY PARAMETER in the string and will not allow you to save the callback URL if it has a query in it.

We tried a dozen callback URL formats that did not involve a string paramter and would involve /Oauth/Oauth.php as the endpoint of the callback URL. None of these worked. We also tried the OAuth1Client.php and OAuth2Client.php as the file on the callback URL, Twitter's api did not process the token request, in fact the module fails to open the dialog box that is needed to verify the username and password for Twitter member. Without the query string in the callback the HybridAuth module DOES NOT WORK AT ALL FOR TWITTER.

Is there a modification we can implement to a file in the module that would allow the module to run while using a callback URL that does not have a query string? What would be the callback URL we would need to use to exchange and verify the token for a user and that would allow HybridAuth to create the user profile information in the Drupal database and Drupal website?

We are also having a similar problem with Tumblr and Amazon, however these social media logon buttons (when you go to the config screens) do not stipulate the webmaster the callback URL format needed and when you to the Tumblr API developer console or the Amazon API Developer console they DO NOT SPECIFIY WHAT THE FORMAT OF THE CALLBACK URL SHOULD BE - because this is specific to the php files and coding setup for the Drupal HybridAUth module.

In other word, each of the main social media logon buttons provided in the module require documentation on what the callback URL format should be but only a handful are furnished in the configuration panels and the rest of them, you can spend weeks trying to guess the format or the end file.

The contributors who put together this module need to append a documentation files that lists the CURRENT VALID CALLBACK URL FORMAT FOR ALL THE MAIN SOCIAL MEDIA BUTTONS/PROVIDERS PACKAGED IN THIS MODULE and this needs to be verified with each of the platforms' technical department before uploading.

For the moment though we would appreciate if you know the callback format for the URLs to Amazon, Tumblr, Facebook, Yahoo, Twitter and Pinterest, if you would please provide them and then a Drupal team should update the module to either include instruction on the configuration panels as currently available for the Twitter and Facebook logins or as part of an addenda to the documentation provided with the module.

Thank you.

Comments

websitetonite created an issue. See original summary.

websitetonite’s picture

avpaderno’s picture

Priority: Major » Normal
Issue tags: -Hybridauth drupal module, -social authentication api, -Drupal module, -Twitter api authentication, -Module incomplete
xurizaemon’s picture