Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Contents        

There's a new Help center!

This documentation page won’t be updated and is going away soon.

Visit https://help.whiteboards.io/ for up-to-date documentation with step-by-step guides, videos, and all the tips&tricks you need to become a Whiteboards master! 


If you already have a paid Whiteboards license in your Atlassian software, connect it and enjoy Pro features in whiteboards.io for all users logging through Atlassian.

To do so, set up an identity provider in whiteboards.io using either OAuth1 or OAuth2. We will then check your Whiteboards license in Atlassian and grant Pro access to all team members logging through that Jira/Confluence instance. You won’t need to purchase additional seats for them.

NOTE: Currently users logging to whiteboards.io with Atlassian Sign-in from Cloud instances won’t be able to see the boards and content previously created in their Whiteboards for Jira & Confluence apps, but can manually export and import their board content. We apologize for this temporary inconvenience. We are working on making our cross-platform experience better in the future.

Connecting Jira/Confluence Data Center/ Server instances (OAuth1)

NOTE: You need to have administrator permissions in Jira/Confluence to perform these actions. Also, the Whiteboards.io backend must be able to reach out to your Atlassian application in order to perform authentication of users and requests. Your firewall should allow this IP address to connect: 35.232.138.12.

  1. Go to your Dashboard.

  2. Click on the vertical ellipsis in the top right corner.

  3. Select Administration.

  4. Under User Management click on Identity providers.

  5. Press Add identity provider.

  6. Choose Atlassian OAuth 1.0a (Application link to Jira or Confluence) and click Next.

  7. Add your Confluence or Jira base URL.

    NOTE: Your Jira or Confluence base URL needs to be on HTTPS. not HTTP.

  8. Select the application type you’re using—Jira or Confluence.

  9. Provide a name for that identity provider and click Next

  10. Click the link under Applink configuration page to open the website where you’ll be able to set up an application link in Atlassian. 

  11. On the administration page that opens, click Create link.

  12. In the window that opens, select Atlassian product as the Application type.

  13. Add https://app.whiteboards.io/ as the Application URL and click Continue.

  14. Confirm the URL by adding https://app.whiteboards.io/ again in the New URL field and click Continue.

  15. Add Whiteboards as the application name.

  16. Choose Generic Application as the application type. 

  17. Make sure that you select to create an incoming link and click Continue.

  18. Switch the browser tab to the whiteboards.io configuration page and click Next.

  19. Make sure it says Whiteboards in the Consumer key and Consumer name fields. 

  20. Copy the public key and switch the browser tab to the application link configuration page. 

  21. Type Whiteboards in the Consumer Key and Consumer Name fields.

  22. Paste the public key to the last field and click Continue. You will see a confirmation that the application link was created successfully. 

  23. Switch the tab back to the whiteboards.io configuration page and click Test connection.

  24. Next, click the Authentication test

  25. On the window that opens, press Allow to connect the software.

  26. Once you see the success message that both connection and authentication tests were successful, click Next.

  27. Make sure that both Allow Incoming and Allow anonymous users are selected.

  28. Open the Allowlist configuration page from the link at the top. 

  29. On the Allowlist page, make sure the two checkboxes under Allow incoming and Allow anonymous users are selected and click Update.

  30. Go back to whiteboards.io and click Test allowlist.

  31. Once you see that the test was successful, click Finish.

  32. Switch back to Jira/Confluence and go to Administration >> Applications >> Application Navigator.
  33. Add Whiteboards in the Name field.

  34. Copy the URL of your organization and add it to the URL field.
    NOTE: Your organization URL looks like this: https://app.whiteboards.io/your-organization-name/. In this example, the URL will be: https://app.whiteboards.io/whiteboards-edu/.

  35. Press Add.

Connecting Jira/Confluence Cloud instances (OAuth2)

  1. Go to your Dashboard.

  2. Click on the vertical ellipsis in the top right corner.

  3. Select Administration.

  4. Under User Management click on Identity providers.

  5. Press Add identity provider.

  6. Choose Atlassian OAuth 2.0 (Jira Cloud or Confluence Cloud) and click Next.

  7. Paste or type just your Atlassian Cloud domain (it’s the word or phrase in your Atlassian URL right after https://).

  8. Provide a name for that identity provider and click Next

  9. Click Authorise to connect your Atlassian account with Whiteboards.

  10. Click Accept to connect. 

  11. Once you see the success screen, click Next.

  12. The system will now check your license status for both Whiteboards for Confluence and Whiteboards for Jira. As a user, you just need access to either Jira or Confluence with a paid Whiteboards license to enjoy Pro features in whiteboards.io. Click Finish to finalize setting up your identity provider.


     

Identity provider added

You will be able to see your identity provider on the list as well as its status. From this view, you can also manage your Whiteboards license in Atlassian, change the configuration of the identity provider, or remove it

All users that select Continue with Atlassian on the login screen will gain access to the organization where that Jira/Confluence instance was connected with an identity provider. No need to purchase additional seats for them and all the Pro features on whiteboards.io will also be unlocked.

In case of any troubles, let us know by raising a ticket with our support and we’ll sort everything out!

  • No labels

This page has no comments.