Skip to content

Providing Configuration & Credentials Securely

Anything that connects analytiQa to your systems (Jira or qTest API tokens, which projects and filters to extract, single sign-on settings) reaches us through a secure credential intake link. Please don't send credentials by email, chat, a support ticket or a shared spreadsheet.


Who to Contact

Work with your Qualtiva technical contact. If you don't know who that is, email support@qualtiva.solutions and we'll put you in touch.

For anything beyond a small change (a new data source, new projects, or first-time onboarding), your technical contact will usually schedule a short session to work through it with you.


How to Request a Change

  1. Email your technical contact (or support@qualtiva.solutions) and ask for a credential intake link.
  2. Describe what you'd like to update, so the link covers exactly the right sections. For example:
    • Connect Jira, or add new Jira filters, boards or projects
    • Add new qTest projects, or change which projects are included
    • Replace an expired or rotated Jira or qTest token
    • Set up or change single sign-on (Microsoft Entra ID / Azure AD)
    • Set up outbound email (SMTP) for alerts and reports
    • Get your URL and credentials for sending data from a CI/CD pipeline or another system (see Publishing Test Results Directly)
  3. Your technical contact sends you a secure link. It's short-lived and valid only for your environment.
  4. Open the link and fill in the requested sections. Your contact can do this with you in the session.
  5. We review and apply the change, then confirm with you. A submission doesn't take effect immediately. We check it first, then roll it out.

Never send tokens or passwords by email or chat

If a token or password has already been shared in email, chat or a ticket, treat it as compromised. Revoke it and create a new one in the source system, then send the new one through a secure link.


The link is on your own analytiQa hostname, in the form https://<your-instance>.analytiqa.cloud/credentials/<token>. Only use links that come from your Qualtiva technical contact.

Short-lived A link expires after a few hours by default. If it has expired, ask for a new one.
Single use for submissions A link that lets you submit stops working as soon as you submit. For another change later, ask for a new link.
Scoped The link shows only the sections your request needs, such as Jira only or qTest only.
Write-only secrets Tokens and passwords you submit are stored encrypted. They can't be read back through the portal, including by you.

Each section has its own on/off switch. Switching a section on and submitting it turns that integration on. Advanced settings, such as the Jira filter configuration, are pre-filled with your current configuration, so you only change what you need.

Viewing your current settings and credentials

Some links, or some tabs of a link, are view-only. They show:

  • Your current non-secret settings (for example, your Jira URL and filter configuration)
  • Credentials analytiQa issues to you, such as the URL, username and password for sending results from a CI/CD pipeline or another system

Ask for a view link whenever you need to look these up. Tokens and passwords you sent us are never shown.


What Each Section Covers

Section What you provide Guide
Jira Jira URL, account email, API token, and the filters that select which issues to extract Jira Extractor Setup
qTest qTest URL, API access token, and which projects to include qTest Extractor Setup
Tosca Cloud Tosca Cloud tenant URL, Token URL, API client ID and secret, and optionally a portal account without MFA Tosca Cloud Extractor Setup
qTest licence & usage A qTest site admin login, used to read licence, session and user-assignment data that qTest's API doesn't provide Discuss with your technical contact
Single sign-on Your Entra ID / Azure AD app registration details (client ID and secret, OpenID Connect metadata URL, issuer, JWKS URI, roles claim) and who should be dashboard admins Discuss with your technical contact
Email (SMTP) Sender name and from-address, SMTP host, port, connection method, username and password, for outbound notifications Discuss with your technical contact

Tosca (Tosca Commander) isn't part of the secure link; Tosca Cloud is. The Tosca extractor runs on a machine in your own network, and your Tosca login (Client ID and Secret, token, or password) goes into its settings on that machine, usually in a session with your technical contact. It never needs to be emailed. The extractor's log shipper does need your send-data URL, username and password, which you can look up with a view link. See Tosca Extractor Setup.

Use the Configuration Checklist to gather everything before your session.