Having issue with our Importer utility for Zephyr for Jira Cloud.Please click here for the steps to resolve the issue. If you are not able to access Capture Cloud and seeing a message, it means your Capture cloud instance is not migrated as part of our GDPR and Atlassian privacy policy. Please click here for the steps to Migrate your Capture Cloud instance to use Capture.
Support | Zephyr

How to Use Capture Browser Extension with  Gsuite SSO User ?

Created on

Steps : 

  1. Once After G suite User Successful Login 
  2. user need to generate API Token for G suite user as show below.
    1. Enter URL-  https://id.atlassian.com/manage/api-tokens  in Browser or Launch manage user account page - https://id.atlassian.com/manage/account-settings where G suite user is logged in, you will get below screen.

    2. Now click on API Token Beta As show below you will get - Create API Token Button in page
    3. After Click on create API Token you will get Below Screen Enter Label like " Capture BE" Click on create.
    4. After Click on Create you will get Below Page to Copy Token

    5. Click on Copy to Clipboard  your Token willl be Copied , we  have to save Token at Some where for Future Use.

  3. After Generating API user can Login in capture BE with API Token as password instead of JIRA User password. like Below.

    Note: During Capture BE authentication(login) as username the email address should be used.
    if we gave user name instead of email we will get below error:
  4. To Avoide that Error we have to Give user Email of Gsuite  Like Below:
  5. After Click on save You can Access Capture Browser with Gsuite user like Below
  6. Now we can perfrom all operation related to BE. (smile)

Note :

If user is deleted API Token or if we are trying to login old Token we get below error.


In above scenarion we need to Revoke the existing API Key or Else they need generate new API Token.

in Below page then They need generate new API Token As mentioned above steps:




If we Click Confirm All APi tokens will be deleted Automatically

Please note this SSO set up used to work fine earlier as they were within the Atlassian domain and hence no change was needed

Was this article helpful?
3 out of 4 found this helpful
Have more questions? Submit a request
Powered by Zendesk