...
- TDS integrated services
- AD groups NOT available - there is NO centralised authorisation or provisioning solution available
- TDS project oriented users and roles management using portal
- 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
- Requires firewall opening 443/tcp from internet to Atlassian Crowd server
- License costs involved - https://www.atlassian.com/software/crowd/pricing
- It provides 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 continuous updates manual CSV/EXCEL sheet mapping between projects, roles and AD groups intended for sync everytime project or groups is created or removed
- total number of mappings is number of projects X number of roles(constant 4) X number of AD groups necessary to be assigned to each project and role
- With example 10 projects and 5 AD groups it might be 10 x 4 x 5 = 200 mappings/lines
- IDM used by some customers
- calling application APIs
- calling TDS APIs (expected to come in the beginning of Q3 2020)
- Atlassian Crowd
- Bitbucket, Confluence or Jira can reach AD directly