Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-2010

Migrate Jira/Confluence to Atlassian Cloud

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: jira, wiki
    • Labels:
      None
    • Similar Issues:

      Description

      Managing Jira/Confluence is time consuming and it would be interesting to move it to respectively Jira Cloud and Confluence cloud.

      I open this ticket to keep track of the evolution of this work.

      Currently the potential migration is blocked by ID-79 as it doesn't support our ldap service

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          oleg_nenashev Oleg Nenashev added a comment -

          yes please!

          Show
          oleg_nenashev Oleg Nenashev added a comment - yes please!
          Hide
          Permalink
          olblak Olivier Vernin added a comment - - edited

          I gave it another try.
          I created a trial account for 'jenkinsci.atlassian.net' (jenkins.atlassian.net is not available anymore)
          While ID-79 progressed, it seems that it's not yet ready for our use case at least there is not "out of the box" solution to sync an openldap service and atlassian cloud.

          The first requirement is to be able to use the same account accross our infrastructure (confluence,artifactory,...) created from here like we do now.

          It appears that we can now sync an azure active directory with atlassian cloud but with several limitation
          1. We cannot sync more than 5000 users as mentionned here. For what I recall, we have more than 60000 ldap users.
          2. We must own domain used by email address authenticated via SAML

          Show
          olblak Olivier Vernin added a comment - - edited I gave it another try. I created a trial account for 'jenkinsci.atlassian.net' (jenkins.atlassian.net is not available anymore) While ID-79 progressed, it seems that it's not yet ready for our use case at least there is not "out of the box" solution to sync an openldap service and atlassian cloud. The first requirement is to be able to use the same account accross our infrastructure (confluence,artifactory,...) created from here like we do now. It appears that we can now sync an azure active directory with atlassian cloud but with several limitation 1. We cannot sync more than 5000 users as mentionned here . For what I recall, we have more than 60000 ldap users. 2. We must own domain used by email address authenticated via SAML
          Hide
          Permalink
          olblak Olivier Vernin added a comment - - edited

          saml-single-sign-on
          Can I get SAML single sign-on for domains that I cannot verify?
          No. To keep products and resources secure, you can only use SAML single sign-on with domains you can verify that you own.

          User provisionning
          You can only sync up to 5,000 users per external directory because some Atlassian products have an upper limit for total supported users. If your external directory has more than 5,000 users, you can still integrate your identity provider, but we'll stop syncing new users after 5,000.

          Show
          olblak Olivier Vernin added a comment - - edited saml-single-sign-on Can I get SAML single sign-on for domains that I cannot verify? No. To keep products and resources secure, you can only use SAML single sign-on with domains you can verify that you own. User provisionning You can only sync up to 5,000 users per external directory because some Atlassian products have an upper limit for total supported users. If your external directory has more than 5,000 users, you can still integrate your identity provider, but we'll stop syncing new users after 5,000.
          Hide
          Permalink
          olblak Olivier Vernin added a comment - - edited

          Several month later, we still can't move to Jira/Confluence cloud because of

          • The user limit of 5000 considering that we are today at 98965 link[link|https://www.atlassian.com/software/jira/pricing]
          • Openldap is not integrated and required us to use Azure AD (not deployed yet) link
            • If we use AzureAd  we have to design a new way to create user account with something similar to accounts.jenkins.io
          • Atlassian cloud only allow users from registered domain, like having jenkins.io email account link
          Show
          olblak Olivier Vernin added a comment - - edited Several month later, we still can't move to Jira/Confluence cloud because of The user limit of 5000 considering that we are today at 98965 link [link|https://www.atlassian.com/software/jira/pricing] Openldap is not integrated and required us to use Azure AD (not deployed yet) link If we use AzureAd  we have to design a new way to create user account with something similar to accounts.jenkins.io Atlassian cloud only allow users from registered domain, like having jenkins.io email account link
          Hide
          Permalink
          timja Tim Jacomb added a comment -

          we moved jira to LF instead

          Show
          timja Tim Jacomb added a comment - we moved jira to LF instead

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            olblak Olivier Vernin
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: