This answer discusses how MettleCI components use external systems for authentication, or how MettleCI components are called by external systems…

Unit Test Harness

The MettleCI Unit Test Harness acts as a bridge between the DataStage engine and your MettleCI Workbench-managed unit test cases. It features no other integrations

MettleCI Workbench

MettleCI does not store users, and instead uses a variety of mechanisms to delegate user management to the technologies with which it interfaces...

Information Server

MettleCI uses your existing Information Server user account (that you use to login to DataStage) to authenticate to Information Server.

Git

Uses an SSH public key to authenticate into your Git platform of choice.

Work Item Management (e.g. Jira)

This is dependent upon your chosen technology, but MettleCI can use SSH keys or OAuth for authentication.

MettleCI Build and Deploy Toolkit

The MettleCI Build and Deploy components are utilised within your chosen build system's build and deployment plans. The interface into these components depends on your chosen technology…

Atlassian Bamboo

MettleCI Build and Deploy components are accessible within Atlassian Bamboo build and deploy plans as Bamboo-native tasks. See the MettleCI Bamboo documentation.

Azure DevOps, GitHub, GitLab, Jenkins, and Others

Other build systems, such as Jenkins, can utilise the full power of MettleCI Build and Deploy components by using the MettleCI command line.

Testing Integration

MettleCI's Compliance Testing, Unit Testing, and End-to-End testing results are available as JUnit-compatible test results, making their integration into your existing testing platform quick and seamless.