> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-scan/ci-cd-integration/generate-security-token.md).

# Generate Security Token

### Generate Security Token - IDE

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FmLD6tcygyMK24rN3RDXA%2Fgenerate_user_access_token.png?alt=media&amp;token=fd3e17b2-8722-478c-ada8-e3cb27dceb79" alt=""><figcaption></figcaption></figure>

1. Security token for configuring **`Access Tokens`** in either `Anypoint Studio` or `VS Code` can be generated from the **`IZ Server`** by following the steps below -

   1. Login to **`IZ Web Application`**. The URL will differ for hybrid and on-premises installations.
   2. Navigate to **`My Account`** main menu. If you are an admin and trying to generate a token on behalf of another user, navigate to **`Organization`** main menu -> **`Tokens`**
   3. Click on **`Generate Token`**, enter the token name, and select **`IZ IDE Developers`** role. Assign **`Custom Rule Publisher`** role, if applicable for the token, which will be used to publish custom rules.

   <br>

   d.Click **`Ok`** to generate the token. **Copy the token and save it securely, as the token will not be displayed again.**&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FXvDQGUZFrm2YjVcEBKPn%2Fiz-token-generated.png?alt=media&amp;token=0d338016-7ae5-4158-b905-17614efbc53c" alt="" width="542"><figcaption></figcaption></figure>

**`NOTE:`** If the Global Setting **`IDE Settings`** -> **`Show All Quality Profiles`** value is set to false, make sure to assign roles specific to the organization.

### Generate Security Token - CICD Scans

1. Security token for configuring **`Auth Token`** in CI/CD scans can be generated from the **`IZ Server`** by following the steps below -
   1. Login to **`IZ Web Application`**. The URL will differ for hybrid and on-premise installations.
   2. Navigate to **`Organization`** main menu -> **`Tokens`**
   3. Click on **`Generate Token`**, enter the token name, and select **`IZ CLI Scanner`** role.&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F1Ip2zSxhqkhTSYh1JK1t%2Fiz-generate-token.png?alt=media&amp;token=3e597d8f-47bd-4fc1-b2a9-a295975550cb" alt="" width="539"><figcaption></figcaption></figure>

d. Click **`Ok`** to generate the token. Copy the token and save it securely as the token will not be displayed again.&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FzZfAMOSy5xsihzOfmno4%2Fiz-token-generated.png?alt=media&amp;token=8b89424e-9142-4dbb-8894-1c0919c08acb" alt="" width="542"><figcaption></figcaption></figure>

### Custom Rule Publisher Role

1. Navigate to **`Organization`** -> **`Roles`** and click on **`Create Role`**
2. Enter the **`Role Name`** and click on next. For example - Custom Rule Publisher&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FUgCqXyde3XZtd9iHnLH2%2Fcustom-rule-publisher-1.png?alt=media&amp;token=b4fb134a-4bb1-416b-a63f-f72d2d75809c" alt="" width="552"><figcaption></figcaption></figure>

3. Select **`Edit Quality Rule`**, **`Activate Rule in Profile`** permissions and click on next&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FTxHFofKeveTA7cOTbvb6%2Fcustom-rule-publisher-2.png?alt=media&amp;token=b8cc3b12-ad8c-494f-9ef0-b6d0ceb37b26" alt="" width="552"><figcaption></figcaption></figure>

4. Submit to create the new role&#x20;

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FAE2zt08ZQLZDSghq76jv%2Fcustom-rule-publisher-3.png?alt=media&amp;token=d37f85ef-3e81-46fa-b5bd-2a100a648dd6" alt="" width="552"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-scan/ci-cd-integration/generate-security-token.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
