OAuth/OpenID Single Sign On (SSO) into Bitbucket using Meetup

Bitbucket OAuth/OpenID app gives the ability to enable OAuth/OpenID Single Sign-On for Bitbucket. Bitbucket is compatible with all OAuth/OpenID Providers. Here we will go through a guide to configure SSO between Bitbucket and Meetup. By the end of this guide, Meetup users should be able to log in and register to Bitbucket.

Pre-requisites

To configure Meetup integration with Bitbucket OAuth / OpenID Connect SSO, you need the following items:

  • Bitbucket should be installed and configured (supported version Bitbucket Server 5.5.0 - 6.10.1, Bitbucket Data Center 5.5.0 - 6.10.1).
  • Admin credentials are set up in Bitbucket.
  • Valid Bitbucket Server and Data center Licence.

Download And Installation

  • Log into your Bitbucket instance as an admin.
  • Navigate to the settings menu and Click Manage Apps.
  • Click Find new apps or Find new add-ons from the left-hand side of the page.
  • Locate Bitbucket OAuth / OpenID Connect Single Sign On (SSO), Bitbucket SSO via search.
  • Click Try free to begin a new trial or Buy now to purchase a license for Bitbucket OAuth / OpenID Connect Single Sign On (SSO), Bitbucket SSO.
  • Enter your information and click Generate license when redirected to MyAtlassian.
  • Click Apply license.
adfs-gif-1

Step 1: Setup Meetup as OAuth Provider

  • Login to Meetup : Go to Meetup API and login to your account.
  • Click on OAuth Consumers tab.
  • OAuth/OpenID/OIDC Single Sign On (SSO), Meetup SSO Login Setup Meetup
  • Create application : Click on "Create New Consumer" or "Create one now".
  • OAuth/OpenID/OIDC Single Sign On (SSO), Meetup SSO Login Create application
  • Consumer name : Name of your Meetupapp.
  • Redirect URI :Copy Callback URL from plugin.
  • Check "Yes, I agree" checkbox for Platform Terms of Service and click on "Register Consumer".
  • NOTE: all the details on the Register OAuth Consumer page are mandatory and need to be filled before clicking on Register Consumer

    OAuth/OpenID/OIDC Single Sign On (SSO), Meetup SSO Login Consumer name
  • Once App is created successfully, you'll see the key and secret of the app.
  • Get Client ID and Client Secret : key is Client ID and secret is client secret.
  • OAuth/OpenID/OIDC Single Sign On (SSO), Meetup SSO Login Get Client ID


Step 2: Setup Bitbucket as OAuth Client

  • Configure Client ID and Client Secret using key and secret value.
  • Scope is optional. All o-authorized clients and API keys are implicitly provided the basic scope.
  • OAuth/OpenID Single Sign On (SSO) into Bitbucket using Meetup- Configure Oauth tab

Step 3: User Profile

    We will be setting up user profile attributes for Bitbucket. If your users are stored in a directory that is Read Only, please check Disable Attribute Mapping in User Profile tab and follow steps given in Matching a User.

    confluence-oauth-openid-sso-user-profile

    a. Finding correct attributes
  • Go to Configure OAuth tab. Scroll down and click on Test Configuration.
  • You will see all the values returned by your Provider to Bitbucket in a table. If you don't see value for First Name, Last Name, Email or Username, make the required settings in your Provider to return this information.
  • Once you see all the values in Test Configuration, keep the window open and go to User Profile tab.
  • b. Setting profile attributes
  • In this tab, fill the values by matching the name of the attribute. For instance, if the Attribute Name in the Test Configuration window is email, enter email against Username.
  • You can configure Email and Username here, otherwise it will create a new user with email address returned in Test Configuration window. If you want existing users to the only login, configure the attribute using which you will match the user in Bitbucket.
  • c. Matching a User
    When the user logs into Bitbucket, one of the user's data/attribute coming in from the Provider is used to search the user in Bitbucket. This is used to detect the user in Bitbucket and log in the user to the same account.
  • Go to User Profile tab.
  • Select Username or Email for Login/Search Bitbucket user account by.
  • Enter the attribute name from Provider which corresponds to Username or Email using Finding Correct Attributes.

Step 4: User Groups

    We will be setting up user group attributes for Bitbucket. If your users are stored in a directory that is Read Only, please check Disable Group Mapping in User Groups tab and skip to Setting default group.

    a. Setting default group
  • Select the users' Default Group in the tab User Groups. If no group is mapped, users are added by default to this group.
  • You can enable default groups for All Users or New Users using the option.Select None if you don't want to assign any default group to SSO users. Using the option Enable Default Groups for.
  • Bitbucket oauth Single Sign On - SSO - Default group
    b. Finding Group Attribute
  • Just like we found Attribute Name for User Profile attributes, we find group attribute.
  • Go to Configure OAuth tab. Scroll down and click on Test Configuration.
  • You will see all the values returned by your OAuth/OpenID Provider to Bitbucket in a table. If you don't see value with groups, make the required settings in your OAuth/OpenID Providerto return group names.
  • Once you see all the values in Test Configuration, keep the window open and go to User Groups tab.
  • Enter the Attribute Name of group against Group Attribute.
  • Check Disable Group Mapping option if you don't want to update groups of existing users.

  • c. Group Mapping
    Group Mapping can be done in two ways:
  • Manual group mapping: If the names of groups in Bitbucket are different than the corresponding groups in OAuth/OpenID Provider, then you should use Manual group mapping.
  • On-The-Fly group mapping: If the names of groups in Bitbucket and OAuth/OpenID Provider are same, you should use On-The-Fly group mapping.

  • I. Manual Group Mapping
    • Check Restrict User Creation Based on Group Mapping option if you want new users to be created only if at least one of the user's OAuth/OpenID Provider groups is mapped to a group in the application.
    • For mapping, first select a Bitbucket group from the dropdown which lists all groups present in Bitbucket and then enter the name of the OAuth/OpenID Provider group to be mapped in the textbox beside
    • For example, if you want all users in 'dev' group in OAuth/OpenID Provider to be added to stash-users, you will need to select stash-users from the dropdown and enter 'dev' against stash-users.
    • Use '+1' and '+10' buttons to add extra mapping fields.
    • Use '-' button next to each mapping to delete that mapping.
    Bitbucket OAuth/OpenID Single Sign On - SSO - Manual group mapping
  • II. On-The Fly Group Mapping
    • Check Create New Groups option if you want new groups from OAuth/OpenID Provider to be created if not found in Bitbucket.
    • If the user is part of some group in Bitbucket and that group is not present in the OAuth/OpenID response returned by OAuth/OpenID Provider, then the user will be removed from that group in Bitbucket.
    • If you don't want On-The-Fly group mapping to affect Bitbucket groups which are managed locally then add those groups in Exclude Groups field.
    Bitbucket OAuth/OpenID Single Sign On - SSO - On the fly group mapping

Step 5: Sign In Settings

    The settings in Sign In Settings tab define the user experience for Single Sign On.
    a. Sign In Settings
  • Set button text for button on login page using Login Button Text.
  • Set redirect URL after login using Relay State. Keep this empty for coming back to the same page user started from.
  • Enable Auto-redirect to Provider if you want to allow users to login only using Provider. Enable backdoor for emergency
  • Backdoor/Emergency URL: Backdoor/Emergency URL gives access to the Application’s default login page. This allows users to log in directly into the application using their local credentials. This will be useful in case the Provider is under maintenance or inaccessible.
  • Domain Restriction : Set domain name which should be allowed for login in Allow Domain. Eg. Allow Domain is miniorange.com then the user with abc@miniorange.com can only able to do login.
  • Bitbucket-OAuth/OpenID-openid-sso-sign-in-settings
    b. Sign Out Settings
  • Set Logout URL or Logout Template to redirect users after logout action.
  • Bitbucket-oauth-openid-sso-sign-in-settings

    c. SSO Error Settings
  • Set the Error message template to build your own error page and redirect users to it in case SSO fails.
  • Bitbucket-oauth-openid-sso-sign-in-settings

Additional Resources




If you are looking for anything which you cannot find, please drop us an email on info@xecurify.com