> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect BMC Helix ITSM (Remedy) with Username & Password (AR-JWT) – StackOne Hub

> Link a BMC Helix ITSM (Remedy) account in the StackOne Hub using Username & Password (AR-JWT). End-user guide to authorize the integration and start using BMC Helix ITSM (Remedy) actions.

<Warning>Use a dedicated BMC Helix service account whose AR System permission groups grant access to the forms your integration needs (Incident, Change, Problem, Task, and Foundation data such as People and Companies). An account without the right permission groups can still connect but will return empty results or permission errors.</Warning>

<section data-guide-section data-guide-scopes="">
  <h2>Find your host</h2>

  <p>Your host is the BMC Helix / AR System server StackOne connects to. Enter it without the scheme (no `https://`) and without a trailing slash or path.</p>

  <ul>
    <li>BMC Helix SaaS: typically a REST-specific host in the form `{company}-restapi.onbmc.com`.</li>
    <li>On-premise: your AR System mid-tier host, often including a port.</li>
    <li>Format: `{company}-restapi.onbmc.com` or `remedy.example.com:8080`</li>
    <li>Example: if you open `https://acme-restapi.onbmc.com/api/arsys/v1/...`, your host is `acme-restapi.onbmc.com`</li>
  </ul>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Use a service-account username and password</h2>

  <p>StackOne authenticates as an AR System user, so provide the login name and password of a dedicated service account.</p>

  <ul>
    <li>Username: the AR System / Helix login name of the service account.</li>
    <li>Example: `stackone.integration`</li>
    <li>Password: the password for that login name.</li>
    <li>The account's AR permission groups and row-level access determine which records StackOne can read and write.</li>
    <li>StackOne exchanges these credentials for a short-lived AR-JWT token automatically and refreshes it as needed — there is no token to paste.</li>
  </ul>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Set an authentication string (only if required)</h2>

  <p>The authentication string is only needed on servers that use Remedy Single Sign-On (RSSO) or multi-tenancy. Most deployments leave it blank.</p>

  <ul>
    <li>Leave blank for standard AR System authentication.</li>
    <li>If your administrator uses RSSO or a tenant/authentication domain, enter the value they provide.</li>
  </ul>
</section>

<div data-whitelabel-hide>
  <h2>Linking the Account from the Hub</h2>

  <Steps>
    <Step title="Navigate to the Hub">
      Use one of the three <a href="/guides/accounts-section#linking-accounts">Linking Account Methods</a> to access the Hub.
    </Step>

    <Step title="Fill out the fields">
      Fill out the following fields using details from your provider:

      <ul>
        <li><strong>Host</strong></li>
        <li><strong>Username</strong></li>
        <li><strong>Password</strong></li>
        <li><strong>Authentication String</strong> (Optional)</li>
      </ul>
    </Step>

    <Step title="Connect">
      <ul>
        <li>Click <strong>Connect</strong></li>
        <li>If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider's authorization flow.</li>
        <li>Once authorization is successful, you will see a confirmation popup</li>
      </ul>
    </Step>
  </Steps>

  <p>If the account linking is successful, you will see the newly linked account in your <a href="/guides/accounts-section">Accounts</a> page.</p>
</div>