メインコンテンツまでスキップ

Workspace Provider Credentials

Some quantum providers are used through Quapp's own credentials and need no setup. Others require your workspace to connect its own provider account before any function can run on them. Those are configured here.

Only a Workspace Admin can manage provider credentials.

Opening the page

Go to Workspace Settings → Manage Credentials.

The page lists the providers that accept a workspace credential:

  • Azure Quantum
  • D-Wave
  • IBM Cloud
  • IBM Quantum

Credential status

Every provider row shows a status. The status controls what you can do with the credential and whether functions may use it.

StatusMeaningAvailable actions
Not ConfiguredNo credential has been registered yetConfigure
UnverifiedSaved, but not yet tested successfullyUpdate, Test Connection, Disable, Delete
ActiveTest Connection succeeded; the credential can be usedUpdate, Test Connection, Disable, Delete
InvalidVerification failed, or the provider rejected the credentialUpdate, Test Connection, Delete
DisabledA configured credential that has been switched offUpdate, Test Connection, Enable, Delete

⚠️ An Unverified credential cannot run jobs. A newly saved credential always starts as Unverified, never as Active. Invoking a function against a provider whose credential is Unverified is blocked, and the interface explains why. Run Test Connection to move the credential to Active.

A Disabled credential can be switched back on with Enable — you do not have to delete it and register it again.

Configuring a credential

  1. In the provider row, open Actions → Configure.
  2. Fill in the provider-specific fields:
    • Azure Quantum — API Key, API Version, Location, Resource Group, Subscription ID, Workspace Name
    • D-Wave — API Token, Endpoint
    • IBM Cloud — API Key, CRN
    • IBM Quantum — the fields shown on the IBM configuration form
  3. Select Save. The row now shows Unverified.
  4. Open Actions → Test Connection.
  5. When the test succeeds, the status becomes Active and Last Validated is updated.

Things to keep in mind

  • A failed Test Connection never turns a credential Active. If the status stays Invalid, use Update to correct the values and test again.
  • Deleting a credential affects every project in the workspace that depends on it. Check the impact before deleting.
  • Credential values are masked in the interface. Never copy them into tickets, reports or source control.
  • Credentials that existed before this feature was introduced were migrated into the status model above and may need a Test Connection before first use.