Announcement

Collapse
No announcement yet.

Enabling google login for vbulletin 5.4.2

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Enabling google login for vbulletin 5.4.2

    I follow this general procedure:

    1 Login with your existing Google account or create a new account if necessary.
    2 Navigate to the Google Developers Console.
    3 Click on the CREATE PROJECT link on top of the page, enter the following value and click on the Create button.
    Project Name: ________ (Whatever)
    4 Return to the list of your projects and wait for the project to be created (Try to refresh the page if you don't see the project yet).
    5 Click on the name of your new project, then on Google APIs in the upper navigation bar and finally on Library on the left side.
    6. First click on the Social APIs \ Google+ API link and then on the Enable link on top.
    If you have a Disable link instead then the API is already enabled and you do not need to make any changes.
    6. Now click on the Credentials link in the left navigation bar and then on OAuth consent screen and enter these values:
    Product name shown to users: ________
    Privacy policy URL: ________ (from your forum)
    8 Now click on the Credentials link in the left navigation bar, then click on the Create credentials button and select OAuth client ID.
    9 Fill out the form with the following values and then click on the Create button.
    Application type: Web application
    Name: ________
    Authorized JavaScript origins: ___________
    Authorized redirect URIs: _________
    10 Copy&paste your OAuth keys into vbulletin.

    What exactly would the two authorized JS origins and redirect URLs be? if say your vbulletin is at https://www.whatever.com/forums

    I am using https://www.whatever.com as the JS URL, and

    https://www.whatever.com/forums as the redirect URL

  • #2
    http://www.whatever.com

    https://www.vbulletin.com/forum/foru...07#post4392407

    However vBulletin Cloud hasn't been upgraded to vBulletin 5.4.2 yet.
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud customization and demonstration site.
    vBulletin 5 Documentation - Updated every Friday. Report issues here.
    vBulletin 5 API - Full / Mobile
    I am not currently available for vB Messenger Chats.

    Comment


    • #3
      If the JavaScript is https://www.whatever.com
      then is the redirect
      https://www.whatever.com/forums
      ?
      (Assuming that /forums is exactly where the forums are)

      Comment


      • #4
        I am asking for clarification from the developer who created this extension.
        Translations provided by Google.

        Wayne Luke
        The Rabid Badger - a vBulletin Cloud customization and demonstration site.
        vBulletin 5 Documentation - Updated every Friday. Report issues here.
        vBulletin 5 API - Full / Mobile
        I am not currently available for vB Messenger Chats.

        Comment


        • #5
          Also please ask - if you click to login via Google, it asks you to choose a Google account, and then if decide not to do it (decide not to proceed) by collapsing the window that asks you to choose a Google account, you get this error:

          Click image for larger version  Name:	GoogleLogin_error_vbulletin.jpeg Views:	1 Size:	46.2 KB ID:	4392415
          I don't think an error should pop up just because you decide against logging in via the social account.

          Comment


          • #6
            Originally posted by MDawg View Post
            If the JavaScript is https://www.whatever.com
            then is the redirect
            https://www.whatever.com/forums
            ?
            (Assuming that /forums is exactly where the forums are)
            The "Authorized redirect URIs" option is not used by the googlelogin plugin (getting the auth code from google is handled by their javascript library). You can leave that value empty.

            I don't think an error should pop up just because you decide against logging in via the social account.
            The error popup is meant to provide tangible feedback to the user that the plugin tried to initiate the auth/link but failed unexpectedly (note that the google auth popup is handled by their JS library, not our plugin).
            At the moment, it's kind of a catch-all whether it failed because of a popup-blocker, or because the user entered in the wrong password when trying to log in to their google account, or in this case because they intentionally closed the window.
            We can probably change it so the last case (intentional close) shows a different message confirming that they are NOT linked/authorized instead of the generic error.
            If you have any ideas on improving the error message (or improvements to the overall flow), could you create an improvement request ticket via the tracker?

            Comment


            • Jin-Soo Jo
              Jin-Soo Jo commented
              Editing a comment
              As a note it seems like when the popup is intentionally closed, google passes "popup_closed_by_user" into the error handler so we can check for that and suppress or change the messaging.

            • MDawg
              MDawg commented
              Editing a comment

          Related Topics

          Collapse

          Working...
          X