Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • TDS integrated services
  • TDS standalone services (only Bitbucket, Confluence or Jira)
    • TDS provides infrastructure
    • TDS maintains application
    • No TDS integration in application
    • Customer key users maintain application (when non system administrator permissions are available)
    • TDS provides assistance with integrations to AD/ADFS or other platforms, so for example AD groups and users sync is possible as there is no interference with TDS
    • AD/ADFS integration possibilities and costs depend mainly on network setup:
      • Bitbucket, Confluence or Jira can reach AD directly
        • AD sync is available using built-in AD functionality
      • Bitbucket, Confluence or Jira cannot reach AD directly
        • Atlassian Crowd
          • Requires on-premise server
          • License costs involved
          • It provides AD sync is available ONLY if Atlassian Crowd is purchased and installed on premise to sync users and groups from AD through Crowd into Bitbucket, Confluence or Jira
          • TDS SSO cannot be used
        • Script workaround
          • Requires on-premise server
          • Needs to be maintained for new versions
          • Slow - it is just script, has quite significant overhead for various API calls
          • Requires manual mapping between projects and AD groups intended for sync
        • IDM used by some customers