Bitbucket is a web-based, Git-based code hosting and collaboration tool for software development teams, and access to the app can be protected using a programmable hardware token (which takes the place of an authentication app).
In order to protect access to Bitbucket using a Fido2 key, you will first need to enable two-factor authentication, then enable authentication using a security key.
Register your FIDO2 key in your Bitbucket account
Before you can use your FIDO2 key as an access method for your Coinbase account you will need to register the key with Coinbase using the following procedure;
- Before you will be able to add a FIDO2 key as an authentication method to your Bitbucket account you will need to enable two-factor authentication.
First, log in to your Bitbucket application using a web browser, then after clicking on the cog icon select the option "Personal Bitbucket settings";
In the left hand column on the web page, and in the section "Security", select the option "Two-step verification";
- Bitbucket is a web-based, Git-based code hosting and collaboration tool for software development teams, and access to the app can be protected using a programmable hardware token (which takes the place of an authentication app).
In order to protect access to Bitbucket using a programmable hardware token, you will first need to enable two-factor authentication.
Enabling two-factor authentication
Two-factor authentication for Bitbucket can be enabled by first logging in to your Bitbucket application using a web browser, then after clicking on the cog icon select the option "Personal Bitbucket settings";
In the left hand column on the web page, and in the section "Security", select the option "Two-step verification";
After selecting this option a QR code will be generated (see example below);
You can use the QR code to program our programmable tokens using the instructions found in the following procedure;
- We have a range of programmable tokens that can act as direct replacements for an authentication apps.
Programming single seeded tokens using a QR code on a windows PC
Download and launch the SafeID/Diamond programming tool.
Click the Scan QR Code button
Before you scan the QR code please ensure that the clock on your computer is displaying the correct date and time.
You can scan the screen for a QR code, or load from a file.
If you are scanning the barcode on the screen please ensure that the QR code is not obscured by other windows, and if you have more than one monitor please ensure that both the app and the QR code are displayed on the main display (display 1).
If you still have difficulty in scanning the QR code double check you only have the one instance of the app running, and that it is the latest version of the app. In most cases when there are issues with scanning of the QR code the most likely cause is the QR code contains the wrong data and may need to be regenerated. To test the QR code you could check that the code works correctly with the authenticator app it is intended for (e.g microsoft authenticator), and if this fails then you know that the QR code will need to be regenerated.
Select Scan Screen.
If succeeded, the Seed box should be filled with the token's seed data.
Now, select your smart card reader from the Reader drop-down list, e.g. "HID OMNIKEY 5427 CK"
Press the Connect button
Now, switch on a SafeID token and place it on the reader.
The tool will read out the token's serial number and time, and display them:
If you want to correct the clock on the token, then leave the "Sync Token Clock" checked, but first ensure the time on your pc is set correctly.
Switch off the token and switch it on again to generate a new code (the token may only use the new seed after being reset)
Programming single seeded tokens using a QR code on an Android mobile phone
Introduction
There are circumstance where you may want to replace a mobile phone based authentication app (such as google authenticator) with a programmable hardware token (such as the SafeID/Diamond or SafeID/Pro programmable tokens).
Preparation
Before you can use an NFC enabled phone to burn programmable tokens you will need to perform the following preparatory steps;
Make sure you’re running the latest version of Android (the majority of new Android smartphones have an NFC chip in the phone).
Turn on your device and slide from the top down to access the android settings.
Maximise the displayed icons then ensure the "NFC" icon is enabled;
If asked if you want to turn on "Android Beam", confirm that you want the feature enabled.
If your mobile device runs android you will need to visit the Google play store and search for the app "Deepnet SafeID Programmer"
Download, Install and run this app.
Before you can produce OTP codes using a programmable token you will need to obtain the seed data (either in the form of a compatible QR code that can be scanned, or in hex or base32 encoded format).
Once the seed data for the token has been obtained it can be transferred to the app either by scanning the QR code, or manual entry of the Base32/Hex encoded seed:
When scanning a QR Code on an Android (or IOS) SafeID programming App you first need to make ensure that the QR code is ready for scanning using the camera on your smartphone.
Display the QR Code ready for scanning (the QR code below is just an example);
Next launch the app on your mobile device,, point the camera at your QR code, then click on
the button;
After clicking on the
the button point the camera the QR code and the code will be automatically scanned;
The token's seed/secret is extracted from the QR code, and you will progress onto the next step "Token Configuration";
You are now ready to burn the seed details onto the token.
Manual entry of the seed may be performed with either a Base32, or Hex encoded seed.
Copy and paste your seed into the input area then click
;
The software will then examine your seed and confirm if it is a valid Base32 or Hex seed (If the programming app cannot identify a valid seed then you may be requested to correct the entry).
When a valid seed has been entered you will still need to confirm the time and algorithm parameters.
Generally speaking, if the token is to be replacing an authentication app, then these parameters can be left at their default settings (but if you are aware that either a different time window size, or algorithm setting are needed, then you will need to manually adjust these settings from the default.
Once the token configuration settings match your requirements click on the
button;
You are now ready to burn the seed details onto the token.
Burning Seed data onto the Programmable Tokens using an NFC enabled smartphone
Once the token parameters have been confirmed you will be asked to turn on the token.
Turn on the token then click
;
The app will update to show that the token is currently not connected to the app;
With NFC on the mobile enabled, ensure your token is turned on, then place the token near the NFC reader on your phone (typically this will be near the top at the back of your phone).
The app will update and show that the token is now connected, and will display details about the token that it has found;
Part of the information displayed is an assessment of any time drift that has been detected on your token.
Generally speaking, if more than 2 seconds drift has been detected we would advise you click on the "Synchronise Token Clock" option prior to burning your token.
If you are ready to burn the token click on the
button, and the token details will be transferred to the token, and you will notified with the message "TOKEN PROGRAMMED SUCCESSFULLY";
Related Articles
Programming single seeded tokens using a QR code on and iOS mobile phone
Introduction
There are circumstance where you may want to replace a mobile phone based authentication app (such as google authenticator) with a programmable hardware token (such as the SafeID/Diamond or SafeID/Pro programmable tokens).
Before you can produce OTP codes using a programmable token you will need to obtain the seed data in the form of a compatible QR code.
Preparation
Before you can use an NFC enabled phone to burn programmable tokens you will need to perform the following preparatory steps;
- Enable NFC on your iOS smartphone
- Install our SafeID programming app on your phone
Enabling NFC
The following procedure can be used to enable NFC on your iOS smartphone;
Installing the SafeID Programmer on your phone
The SafeID programming app is available for download in versions suitable for Windows, Android and iOS devices.
Instructions for downloading the programming app on your iOS device;
If your mobile device runs android you will need to visit the apple play store and search for the app "SafeID Programmer"
Download, Install and run this app.
Burning Seed data onto the Programmable Tokens using an NFC enabled smartphone
When scanning a QR Code on an Android (or IOS) SafeID programming App you first need to make ensure that the QR code is ready for scanning using the camera on your smartphone.
Display the QR Code ready for scanning (the QR code below is just an example);
Next launch the app on your mobile device, and use the following instructions to burn the programmable token;
Launch the app, point the camera at your QR code, then click on
the button to scan the image;After the QR Code has been scanned you will find that the seed details have been automatically added to the app and you will be ready to burn the seed details onto the token.
Switch on the programmable token and place it against the back of the phone, then use the
button to start burning the token.When you hear a beep, do not move the token until you hear the second beep, and the message "Token programmed successfully" will be displayed (indicating that the token has been programmed).
Related Articles
Programming multi-seeded tokens
If you have a multi seeded programmable token (such as the SafeID PinPad(pro) or SafeID QR(pro), then please see the instructions in the following guides;
Related Articles
Verifying your token
Once you have programmed your token you will need to verify it with Bitbucket.
At the "Enter the resulting verification code:" prompt, copy a 6-digit code from your newly programmed hardware token , then click
;
You will then be notified that an email has been sent to you (in order to verify enabling of 2fa on your account);
Open the email sent to you, then from within the email, click on the link
Two-step verification should then be enabled for your account.
Related Articles
Once two-step authentication has been enabled, scroll down the option settings until you reach the section "Security keys".
Under the prompt "Device name", provide a suitable name for your key then click on the button "Add security key";
When asked where to save this passkey, select the option "Security Key", then click
;
You are now notified that access to google will be prepared with your Fido2 security key - click
to proceed to the next step;
You will asked for permission to examine your Fido2 key, insert the key into a USB port then click
;
You will now be asked to touch the Fido2 key (in the case of a Fido key with a fingerprint reader you will need to swipe your finger on the key);
Provided you press the button on the Fido2 key in the allowed time, the passkey details will be stored on your Fido2 key, and you will be presented with the following confirmation;
Click "OK", and the FIIDO2 key will be registered with Bitbucket, and is ready to be used when you next log in.
Signing in to Bitbucket with a FIDO2 key
Once you have registered you FIDO2 key with Bitbucket the key will be ready to be used as an authentication method when accessing your account;
- When you next sign in to the your Bitbucket account, you will be prompted to select a passkey select the option "Security key";
Insert you key into a suitable port and the screen will now prompt you to touch the key;
After touching the button on your Fido key you will be logged in to your Bitbucket account.
Related Articles
